libnvdimm/labels: Fix divide error in nd_label_data_init()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.238, 5.15.185, 5.4.294, 6.1.141, 6.12.31, 6.14.9, 6.6.93
- CVEs
- CVE-2025-38072
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 20:56 UTC · Revision 1
Source evidence
libnvdimm/labels: Fix divide error in nd_label_data_init()
core-osv · Original sourcePublished 18 Jun 2025, 09:33 UTC
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.
osv:CVE-2025-38072
Kernel
Fixed versions: 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9
Complete source record
{
"id": "2747b1f7e1420413432f0588a9355833869fd63ea52a07e6b96788d54f7cfc8b",
"url": "https://osv.dev/vulnerability/CVE-2025-38072",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "libnvdimm/labels: Fix divide error in nd_label_data_init()",
"summary": "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.",
"evidence": "osv:CVE-2025-38072",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.294",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.238",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.185",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.141",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.93",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.31",
"evidence": "/affected/1/ranges"
},
{
"value": "6.14.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38072",
"aliases": [
"CVE-2025-38072"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7d47aad4570e5e6e9a8162bb417ca9b74132f27c"
},
{
"fixed": "2bd4a938d2eda96ab7288b8fa5aae84a1de8c4ca"
},
{
"fixed": "396c46d3f59a18ebcc500640e749f16e197d472b"
},
{
"fixed": "f49c337037df029440a8390380dd35d2cf5924d3"
},
{
"fixed": "db1aef51b8e66a77f76b1250b914589c31a0a0ed"
},
{
"fixed": "ea3d95e05e97ea20fd6513f647393add16fce3b2"
},
{
"fixed": "1d1e1efad1cf049e888bf175a5c6be85d792620c"
},
{
"fixed": "e14347f647ca6d76fe1509b6703e340f2d5e2716"
},
{
"fixed": "ef1d3455bbc1922f94a91ed58d3d7db440652959"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38072.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.294"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.238"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.185"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.141"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.93"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.31"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.14.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38072.json"
}
}
],
"modified": "2026-10-28T02:30:39.508327022Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/1d1e1efad1cf049e888bf175a5c6be85d792620c",
"https://git.kernel.org/stable/c/2bd4a938d2eda96ab7288b8fa5aae84a1de8c4ca",
"https://git.kernel.org/stable/c/396c46d3f59a18ebcc500640e749f16e197d472b",
"https://git.kernel.org/stable/c/db1aef51b8e66a77f76b1250b914589c31a0a0ed",
"https://git.kernel.org/stable/c/e14347f647ca6d76fe1509b6703e340f2d5e2716",
"https://git.kernel.org/stable/c/ea3d95e05e97ea20fd6513f647393add16fce3b2",
"https://git.kernel.org/stable/c/ef1d3455bbc1922f94a91ed58d3d7db440652959",
"https://git.kernel.org/stable/c/f49c337037df029440a8390380dd35d2cf5924d3",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html",
"https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38072.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38072",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38072.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38072",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 506940,
"published_at": "2025-06-18T09:33:48.666+00:00"
}