nvdimm/btt: reject an arena whose nfree is below the lane count
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5212e11fde4d40fa627668b4f2222d20db488f71 · < 6b1faf1f099f7060b5f1f2f0d024132581f1726e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nvdimm/btt: reject an arena whose nfree is below the lane count
The BTT info block's nfree field, the number of reserve free blocks, is read from the medium without validation. btt_freelist_init() and btt_rtt_init() size the per-lane freelist[] and rtt[] arrays by nfree, but the I/O path indexes them by the lane from nd_region_acquire_lane(), which is bounded by nd_region->num_lanes (ND_MAX_LANES), not by nfree. A crafted or foreign arena whose nfree is below the lane count makes freelist[lane]/rtt[lane] run past the allocation: an out-of-bounds write.
btt.rst documents the nlanes = min(nfree, num_cpus) invariant, which the code does not currently honor: num_lanes is ND_MAX_LANES regardless of nfree. Reject an arena whose nfree is below num_lanes at discovery, before the per-lane arrays are allocated, enforcing that invariant.
From the CVE record · Linux
The Linux kernel’s nvdimm/btt code does not validate an arena’s nfree value against its lane count. A crafted or foreign arena with nfree below the lane count can cause an out-of-bounds write during I/O. The input does not specify an authentication requirement or whether user interaction is needed.
Engineers running Linux kernels with nvdimm/btt should check their deployments; affected versions are not specified.