Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-99224: keys: Protect the type name while describing a key

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 0461bc8f91116aae4a020e15f4e1c1fd535ab35e, 19c4de819e52b7f606468fbfe4fcef4e812e2777, 3c3cfd9e262afc9558c38f8cec57f09d10988546.

Low priority for now. Upgrade to Linux Linux 0461bc8f91116aae4a020e15f4e1c1fd535ab35e, 19c4de819e52b7f606468fbfe4fcef4e812e2777, 3c3cfd9e262afc9558c38f8cec57f09d10988546 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: keys: Protect the type name while describing a key keyctl_describe_key() must keep the key type's name alive until kasprintf() has consumed it. The retained key reference keeps the key and its description alive, but does not pin the module providing its type. The name is passed to kasprintf() without holding key->sem. kvasprintf() uses the saved name pointer in two formatting passes, with a GFP_KERNEL allocation between them. With AF_RXRPC=m, a task that passes View permission before type retirement can overlap a privileged module unload in this order: 1. KEYCTL_DESCRIBE looks up the key, saves key->type->name in the kasprintf() arguments and completes the first formatting pass. 2. While the formatter is delayed before its second pass, af_rxrpc_exit() calls unregister_key_type(), which removes the type from the registry and waits for key_gc_keytype(). 3. The collector takes key->sem for writing, retypes the retained key to key_type_dead and completes retirement. Unregistration and module exit return, allowing free_module() to release the type and name. 4. The formatter resumes its second pass and reads the saved name from released module storage, which can fault in string(). Hold key->sem for reading across kasprintf(). The collector then cannot retype the key or complete retirement until both formatting passes have finished. If retirement wins the lock first, formatting uses the core key_type_dead name instead. Release the semaphore immediately after kasprintf(), including on allocation failure, before copying to userspace. Oops report as below: BUG: unable to handle page fault for address: fffffbfff8054794 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page RIP: 0010:string+0x23f/0x470 Call Trace: vsnprintf+0x330/0x1110

HighCVSS 7.0 · v3.1—No exploit Fix available
Published
Nov 2, 2026
Updated
Nov 3, 2026
EPSS
0.1% · 1th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.0
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99224

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.18affected
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before 19c4de819e52b7f606468fbfe4fcef4e812e2777affected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before a49e6c9a1a5b3457c946a8efb616ce13b4ca8194affected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before 916667df7695366f23cfaf365b5840b228cc4b2eaffected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before dddd3a1ab7d12ee163477918ff6eb943361db4feaffected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before 3c3cfd9e262afc9558c38f8cec57f09d10988546affected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before 6b613747f7ea309ada5b8d05b55398c338f7a968affected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before dea367df18e3a4faac393e3a4e818ee03af89b19affected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before 0461bc8f91116aae4a020e15f4e1c1fd535ab35eaffected · git
    • aa9d4437893f7e015ce5b6d6c443a9ba92c8a2e7 and later · before fced7238b7e80cf8aa688d5af976e4aa6e33c329affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.115-16.12.115-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99222Nov 2, 2026 · keys: Protect the read method check against type removal
    0Monitor
  • ← EarlierCVE-2026-99223Nov 2, 2026 · keys: make keyring indexes independent of kernel addresses
    0Monitor
  • Later →CVE-2026-99225Nov 2, 2026 · keys: Check the authorization payload in process keyring searches
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0461bc8f91116aae4a020e15f4e1c1fd535ab35eVendor (CNA)
Linux Linux19c4de819e52b7f606468fbfe4fcef4e812e2777Vendor (CNA)
Linux Linux3c3cfd9e262afc9558c38f8cec57f09d10988546Vendor (CNA)
Linux Linux6b613747f7ea309ada5b8d05b55398c338f7a968Vendor (CNA)
Linux Linux916667df7695366f23cfaf365b5840b228cc4b2eVendor (CNA)
Linux Linuxa49e6c9a1a5b3457c946a8efb616ce13b4ca8194Vendor (CNA)
Linux Linuxdddd3a1ab7d12ee163477918ff6eb943361db4feVendor (CNA)
Linux Linuxdea367df18e3a4faac393e3a4e818ee03af89b19Vendor (CNA)
Linux Linuxfced7238b7e80cf8aa688d5af976e4aa6e33c329Vendor (CNA)
debian:linux6.12.115-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+3 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓
  2. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records