CVE-2026-99222: keys: Protect the read method check against type removal
Noroxi assessment
Priority: Monitor (action score 0/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.18% (FIRST EPSS).
- Fixed version: Linux Linux 1486caee47b4909f52835a957c3293e970113e44, 3edc064069d07e7d37359fcb4d03d3bab15ee3ab, 4.15.
Low priority for now. Upgrade to Linux Linux 1486caee47b4909f52835a957c3293e970113e44, 3edc064069d07e7d37359fcb4d03d3bab15ee3ab, 4.15 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 read method check against type removal keyctl_read_key() checks key->type->read without holding key->sem. A reference keeps the key alive, but does not pin the module containing its type. A surviving RxRPC key can therefore be read while AF_RXRPC is being unloaded: KEYCTL_READ task Module unload and key GC ---------------- ------------------------ lookup_user_key() permission / possession checks load key->type af_rxrpc_exit() unregister_key_type() GC: down_write(key->sem) GC: retype to key_type_dead GC: up_write(key->sem) unregister_key_type() returns free_module() read saved type's read member The final access can read freed module storage. The read invocation in __keyctl_read_key() is already protected by key->sem, but the earlier method check is outside that critical section. Move the method check into __keyctl_read_key(), after key_validate() and under its existing read hold on key->sem. The check and invocation then use the same protected type for length queries and every read retry. The GC cannot retype the key until the semaphore is released, and type unregistration waits for that GC pass before the module can be freed. Return -EOPNOTSUPP when validation succeeds and the type has no read method. A temporary buffer may now be allocated before this result; allocation and copying to userspace remain outside the semaphore.
- Published
- Nov 2, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 7fa67aa30509ad0da72ac0f757aa76e53c0ea3de, 18779eac17b5df9dff57138d07631573553a41d4, f1afcf9488fc45765e20e2047d3b776981900e0b, 212d3adb1af4e34acb158d6c6def370016a1011d, 5.7affected
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before e5f830ae6611cddbfc504c43f14155f60b63206aaffected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before ff11cfed85cbfdd7fe1185ebd18d2c7a8353ad8daffected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before 1486caee47b4909f52835a957c3293e970113e44affected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before ff44f1b303aa76a818d898e85c56ed4852c031e2affected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before 6a36e2a1a017c51f8a8ad2a094566bad97c46a9baffected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before 3edc064069d07e7d37359fcb4d03d3bab15ee3abaffected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before cf1af7df80e38bf58bd74c2cccce32fcbd1a596aaffected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before e2a2deda08d91644f5e30c17d267b1cdc5f124b2affected · git
- d3ec10aa95819bff18a0d936b18884c7816d0914 and later · before 925c84e3cc21caf09de92d9bcafab0147790debfaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-1 | 6.12.115-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99220Nov 2, 2026 · asymmetric_keys: reject trust keys without IDs0Monitor
- ← EarlierCVE-2026-99221Nov 2, 2026 · keys/trusted_keys: return immediately after TPM unseal failure0Monitor
- Later →CVE-2026-99223Nov 2, 2026 · keys: make keyring indexes independent of kernel addresses0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1486caee47b4909f52835a957c3293e970113e44 | Vendor (CNA) |
| Linux Linux | 3edc064069d07e7d37359fcb4d03d3bab15ee3ab | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5.7 | Vendor (CNA) |
| Linux Linux | 6a36e2a1a017c51f8a8ad2a094566bad97c46a9b | Vendor (CNA) |
| Linux Linux | 925c84e3cc21caf09de92d9bcafab0147790debf | Vendor (CNA) |
| Linux Linux | cf1af7df80e38bf58bd74c2cccce32fcbd1a596a | Vendor (CNA) |
| Linux Linux | e2a2deda08d91644f5e30c17d267b1cdc5f124b2 | Vendor (CNA) |
| Linux Linux | e5f830ae6611cddbfc504c43f14155f60b63206a | Vendor (CNA) |
| Linux Linux | ff11cfed85cbfdd7fe1185ebd18d2c7a8353ad8d | Vendor (CNA) |
| Linux Linux | ff44f1b303aa76a818d898e85c56ed4852c031e2 | Vendor (CNA) |
| debian:linux | 6.12.115-1 · Debian:13 | Package 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.
- Published
- Fix recordedsame day
- TodayNov 5, 2026+3 d
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 researchersFinders, 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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/3edc064069d07e7d37359fcb4d03d3bab15ee3ab
- git.kernel.org/stable/c/6a36e2a1a017c51f8a8ad2a094566bad97c46a9b
- git.kernel.org/stable/c/925c84e3cc21caf09de92d9bcafab0147790debf
- git.kernel.org/stable/c/cf1af7df80e38bf58bd74c2cccce32fcbd1a596a
- git.kernel.org/stable/c/e2a2deda08d91644f5e30c17d267b1cdc5f124b2
- git.kernel.org/stable/c/e5f830ae6611cddbfc504c43f14155f60b63206a
- git.kernel.org/stable/c/ff11cfed85cbfdd7fe1185ebd18d2c7a8353ad8d
- git.kernel.org/stable/c/ff44f1b303aa76a818d898e85c56ed4852c031e2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.