Skip to main content
VulnerabilityPublished Updated

CVE-2025-38072: Linux kernel · libnvdimm/labels: Fix divide error in nd_label_data_init()

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 5 Nov 2026, 21:19 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in f49c337037df029440a8390380dd35d2cf5924d3, ef1d3455bbc1922f94a91ed58d3d7db440652959, ea3d95e05e97ea20fd6513f647393add16fce3b2 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2025

  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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < f49c337037df029440a8390380dd35d2cf5924d3
Fixed in
  • f49c337037df029440a8390380dd35d2cf5924d3
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < ef1d3455bbc1922f94a91ed58d3d7db440652959
Fixed in
  • ef1d3455bbc1922f94a91ed58d3d7db440652959
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < ea3d95e05e97ea20fd6513f647393add16fce3b2
Fixed in
  • ea3d95e05e97ea20fd6513f647393add16fce3b2
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < e14347f647ca6d76fe1509b6703e340f2d5e2716
Fixed in
  • e14347f647ca6d76fe1509b6703e340f2d5e2716
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < db1aef51b8e66a77f76b1250b914589c31a0a0ed
Fixed in
  • db1aef51b8e66a77f76b1250b914589c31a0a0ed
LinuxLinuxAffected
  • ≥ 7d47aad4570e5e6e9a8162bb417ca9b74132f27c, < 396c46d3f59a18ebcc500640e749f16e197d472b
Fixed in
  • 396c46d3f59a18ebcc500640e749f16e197d472b

Description

In the Linux kernel, the following vulnerability has been resolved: libnvdimm/labels: Fix divide error in nd_label_data_init() If a faulty CXL memory device returns a broken zero LSA size in its memory device information (Identify Memory Device (Opcode 4000h), CXL spec. 3.1, 8.2.9.9.1.1), a divide error occurs in the libnvdimm driver: Oops: divide error: 0000 [#1] PREEMPT SMP NOPTI RIP: 0010:nd_label_data_init+0x10e/0x800 [libnvdimm] Code and flow: 1) CXL Command 4000h returns LSA size = 0 2) config_size is assigned to zero LSA size (CXL pmem driver): drivers/cxl/pmem.c: .config_size = mds->lsa_size, 3) max_xfer is set to zero (nvdimm driver): drivers/nvdimm/label.c: max_xfer = min_t(size_t, ndd->nsarea.max_xfer, config_size); 4) A subsequent DIV_ROUND_UP() causes a division by zero: drivers/nvdimm/label.c: /* Make our initial read size a multiple of max_xfer size */ drivers/nvdimm/label.c: read_size = min(DIV_ROUND_UP(read_size, max_xfer) * max_xfer, drivers/nvdimm/label.c- config_size); Fix this by checking the config size parameter by extending an existing check.

References

Community reviews

Loading reviews…