Skip to main content
Menu
CVEs

Linux kernel wrong-offset memory read in configfs subsystem callbacks

CVE-2026-99486Published November 19, 2026, updated

Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

In the Linux kernel, the following vulnerability has been resolved:

rust: configfs: fix data offset calculation for subsystem callbacks

get_group_data() chooses between Group::<Parent>::container_of() and Subsystem::<Parent>::container_of() based on whether this represents the root group of a configfs subsystem. It detects this by checking (*this).cg_subsys.is_null(), but link_group() in fs/configfs/dir.c unconditionally sets cg_subsys for every config_group attached anywhere in a registered subsystem, including the subsystem's own su_group. The only config_group with a NULL cg_subsys is the configfs root, on which userspace cannot trigger callbacks. The check is therefore always false at runtime, and the Subsystem branch is dead. Subsystem-level callbacks reach the Group branch and may read data at the wrong offset.

Thus change the is_root check to correctly identify whether a group is a root group by comparing this to subsys.su_group.

[ Andreas: Fix clippy warning on 1.85.0 by moving safety comment. ]

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-99486 (rust: configfs: fix data offset calculation for subsystem callbacks), 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-99486 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 6.16
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99486 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99486 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/dc1744584b2b9cd8a04e1b824f72bfec0e3c3374
- https://git.kernel.org/stable/c/b91e8d8c2ed97b49a2fd6c2c9516586a8f2aa3c0
- https://git.kernel.org/stable/c/e84c9b64df615e658e47561b835c1364dc48f0c0
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-99486
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-99486"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-99486

Is CVE-2026-99486 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-99486?

Linux: version 6.16.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.