Linux kernel buffer overflow
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
In the Linux kernel, the following vulnerability has been resolved:
cxl/features: Ensure that count is set before access to ent[] __counted_by()
get_supported_features() assigns entries->num_features only after the memcpy() loop that fills entries->ent[] has already run. Since ent[] is __counted_by(num_features), the compiler's bounds instrumentation sees a 0-length array during that loop and FORTIFY_SOURCE trips on the memcpy. Set @num_features right after allocation, before any write into ent[], so the bound is correct for the whole lifetime of the array.
This was found via a fortify panic:
memcpy: detected buffer overflow: 384 byte write of buffer size 0 WARNING: lib/string_helpers.c:1035 at __fortify_report+0x54/0xa0 kernel BUG at lib/string_helpers.c:1043! Call trace: __fortify_panic+0x10/0x18 get_supported_features.isra.0+0x4a0/0x4d0 [cxl_core] devm_cxl_setup_features+0x84/0x120 [cxl_core] cxl_pci_probe+0x254/0x5e0 [cxl_pci]
Same class of bug, same fix shape as commit 6c9d2e87df40 ("cxl/fwctl: Fix __fortify_panic"), which fixed the analogous issue in cxlctl_get_supported_features() but missed this one.
[ dj: Fixed up title typo per Jonathan. ]
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99795 (cxl/features: Ensure that count is set before access to ent[] __counted_by()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99795 (entry last updated 2026-11-20):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 6.15
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99795 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99795 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/63714fa4033b51ce615be6f083be0b19847d0d1e
- https://git.kernel.org/stable/c/deb8b87c027db150de626a5808f648b1e52d90a1
- https://git.kernel.org/stable/c/c1031c2474f73261d8d5e4deef2b5dc20fb964f5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99795
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99795"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux6.15
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99795 |
| Record | NVD · CVE-2026-99795 |
| Other links 3 | |
| Link | git.kernel.org · stable/c/63714fa4033b51ce615be6f083be0b19847d0d1e |
| Link | git.kernel.org · stable/c/deb8b87c027db150de626a5808f648b1e52d90a1 |
| Link | git.kernel.org · stable/c/c1031c2474f73261d8d5e4deef2b5dc20fb964f5 |
Questions about CVE-2026-99795
Is CVE-2026-99795 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99795?
Linux: version 6.15.
Source: cve.now feed data
Related
- CVE-2026-99794Bluetooth: L2CAP: Reject signalling responses in invalid states
- CVE-2026-99793Bluetooth: L2CAP: Only accept connection responses to outstanding requests
- CVE-2026-99792smb/server: prevent file publication after tree disconnect
- CVE-2026-99791xfs: improve dirent bounds checking in scrub and repair
- CVE-2026-99790NFSD: stop registering with rpcbind after a failure in listener_set
- CVE-2026-99789block: restore the iterator when rejecting a misaligned bio
No corrections so far. Something wrong on this page? Report an error.