Skip to main content
VulnerabilityPublished

CVE-2026-99442: Linux kernel · nvmem: core: Fix OOB read for bit offsets of more than one byte

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99442· Medium

Not known to be exploited · fixed in 24530401e8001aaa637dd5007fcdc6fbc00300be : update Linux kernel when convenient.

Data as of 19 Nov 2026, 17:49 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 24530401e8001aaa637dd5007fcdc6fbc00300be, 91895cfc28aed7c5daad13475c68588a844843d8, 006ad1a97ab79f0173e44d82f75340243b54024b +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.12.31 <6.12.117
  • >=6.14.9 <6.15
Fixed in
  • 24530401e8001aaa637dd5007fcdc6fbc00300be
  • 91895cfc28aed7c5daad13475c68588a844843d8
  • 006ad1a97ab79f0173e44d82f75340243b54024b
  • 6.15
  • 6.12.117
  • 2b76fa7fb0a44ded2367e51b1d296f962854301f
LinuxLinuxAffected
  • =6.15
Fixed in–

Description

A vulnerability in the Linux kernel's nvmem core component causes an out-of-bounds (OOB) read when bit offsets are equal to or exceed one byte. The flaw arises because the read position is advanced by a byte offset, but the per-byte read loop does not account for this, leading to reading beyond the intended memory bounds. Although the out-of-bounds data read is cleared and does not leak directly, this behavior was detected by KASAN during memory error analysis.

References

Community reviews

Loading reviews…