Skip to content
statance
MenuClose
unknown

CVE-2026-99442

nvmem: core: Fix OOB read for bit offsets of more than one byte

Published 19 Nov 2026 · Source updated 19 Nov 2026 · Retrieved 2026-11-19 15:23 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

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

nvmem: core: Fix OOB read for bit offsets of more than one byte

When the bit offset is BITS_PER_BYTE or larger the read position is advanced by `bytes_offset`. This is not taken into account in the per-byte read loop which still reads `cell->bytes` resulting in an out of bounds read of `bytes_offset` bytes. The information read OOB does not leak directly as the erroneously read bits are cleared.

Detected by KASAN while looking for a use-after-free in simplefb.c.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: a4f865ecdbdd2b466f7914c293246c3c13654fc4 to < 2b76fa7fb0a44ded2367e51b1d296f962854301f; affected: 7a06ef75107799675ea6e4d73b9df37e18e352a8 to < 006ad1a97ab79f0173e44d82f75340243b54024b; affected: 7a06ef75107799675ea6e4d73b9df37e18e352a8 to < 91895cfc28aed7c5daad13475c68588a844843d8; affected: 7a06ef75107799675ea6e4d73b9df37e18e352a8 to < 24530401e8001aaa637dd5007fcdc6fbc00300be; affected: 4ff5631498091f82f3abdf7db15e888fe60ee572; affected: 6.12.31 to < 6.12.117; affected: 6.14.9 to < 6.15See vendor advisory
LinuxLinuxaffected: 6.15; unaffected: 0 to < 6.15; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed