cxl: Fix race of nvdimm_bus object when creating nvdimm objects
In the Linux kernel, the following vulnerability has been resolved: cxl: Fix race of nvdimm_bus object when creating nvdimm objects Found issue during running of cxl-translate.sh unit test. Adding a 3s sleep right before the test seems to make the issue reproduce fairly consistently. The cxl_translate module has dependency on cxl_acpi and causes orphaned nvdimm objects to reprobe after cxl_acpi is removed. The nvdimm_bus object is registered by the cxl_nvb object when cxl_acpi_probe() is called. With the nvdimm_bus object missing, __nd_device_register() will trigger NULL pointer dereference when accessing the dev->parent that points to &nvdimm_bus->dev. [ 192.884510] BUG: kernel NULL pointer dereference, address: 000000000000006c [ 192.895383] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS edk2-20250812-19.fc42 08/12/2025 [ 192.897721] Workqueue: cxl_port cxl_bus_rescan_queue [cxl_core] [ 192.899459] RIP: 0010:kobject_get+0xc/0x90 [ 192.924871] Call Trace: [ 192.925959] <TASK> [ 192.926976] ? pm_runtime_init+0xb9/0xe0 [ 192.929712] __nd_device_register.part.0+0x4d/0xc0 [libnvdimm] [ 192.933314] __nvdimm_create+0x206/0x290 [libnvdimm] [ 192.936662] cxl_nvdimm_probe+0x119/0x1d0 [cxl_pmem] [ 192.940245] cxl_bus_probe+0x1a/0x60 [cxl_core] [ 192.943349] really_probe+0xde/0x380 This patch also relies on the previous change where devm_cxl_add_nvdimm_bridge() is called from drivers/cxl/pmem.c instead of drivers/cxl/core.c to ensure the dependency of cxl_acpi on cxl_pmem. 1. Set probe_type of cxl_nvb to PROBE_FORCE_SYNCHRONOUS to ensure the driver is probed synchronously when add_device() is called. 2. Add a check in __devm_cxl_add_nvdimm_bridge() to ensure that the cxl_nvb driver is attached during cxl_acpi_probe(). 3. Take the cxl_root uport_dev lock and the cxl_nvb->dev lock in devm_cxl_add_nvdimm() before checking nvdimm_bus is valid. 4. Set cxl_nvdimm flag to CXL_NVD_F_INVALIDATED so cxl_nvdimm_probe() will exit with -EBUSY. The removal of cxl_nvdimm devices should prevent any orphaned devices from probing once the nvdimm_bus is gone. [ dj: Fixed 0-day reported kdoc issue. ] [ dj: Fix cxl_nvb reference leak on error. Gregory (kreview-0811365) ]
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 0th percentile
- CWE
- CWE-362
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.14.1 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel5.14
- linux linux kernel7.0
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
- 5.14affected
- 8fdcb1704f61a8fd9be0f3849a174d084def0666 and later · before 5fc4e150c5ada5f7d20d8f9f1b351f10481fbdf7affected · git
- 8fdcb1704f61a8fd9be0f3849a174d084def0666 and later · before 5b230daeee420833287cc77314439903e5312f10affected · git
- 8fdcb1704f61a8fd9be0f3849a174d084def0666 and later · before 96a1fd0d84b17360840f344826897fa71049870eaffected · git
- before 5.14not affected · semver
- 6.18.17 and later · up to and including 6.18.*not affected · semver
- 6.19.7 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
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 | all versions | — |
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.38.1.160000.2.22 | 6.12.0-160000.38.1.160000.2.22 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.38.1 | 6.12.0-160000.38.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 5b230daeee420833287cc77314439903e5312f10 | Vendor (CNA) |
| Linux Linux | 5fc4e150c5ada5f7d20d8f9f1b351f10481fbdf7 | Vendor (CNA) |
| Linux Linux | 96a1fd0d84b17360840f344826897fa71049870e | Vendor (CNA) |
| debian:linux | 6.19.8-1 · Debian:14 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.38.1.160000.2.22 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.38.1 · openSUSE:Leap 16.0 | 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.
No dated events beyond publication.
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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/5b230daeee420833287cc77314439903e5312f10
- git.kernel.org/stable/c/5fc4e150c5ada5f7d20d8f9f1b351f10481fbdf7
- git.kernel.org/stable/c/96a1fd0d84b17360840f344826897fa71049870e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.