Skip to main content
VulnerabilityPublished Updated

CVE-2026-46159: Linux kernel · btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:34 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-06.

Patch
Available – fixed in f407aad350bdea4db300c47433573b7a41630d33, f5ee467b56764964027c361641f64953fc0f8f9a, d8224b1be6627c6c3b204bfb264508d27c65ac44 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 May 2026

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

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < f407aad350bdea4db300c47433573b7a41630d33
Fixed in
  • f407aad350bdea4db300c47433573b7a41630d33
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < f5ee467b56764964027c361641f64953fc0f8f9a
Fixed in
  • f5ee467b56764964027c361641f64953fc0f8f9a
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < d8224b1be6627c6c3b204bfb264508d27c65ac44
Fixed in
  • d8224b1be6627c6c3b204bfb264508d27c65ac44
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < d69a4a6813fdba7c4cc3695a7e843842b240790d
Fixed in
  • d69a4a6813fdba7c4cc3695a7e843842b240790d
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < d09d67d5de577cedae3de9497dff217e0ac8b641
Fixed in
  • d09d67d5de577cedae3de9497dff217e0ac8b641
LinuxLinuxAffected
  • ≥ 7fde62bffb576d384ea49a3aed3403d5609ee5bc, < 973e57c726c1f8e77259d1c8e519519f1e9aea77
Fixed in
  • 973e57c726c1f8e77259d1c8e519519f1e9aea77

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak btrfs_ioctl_space_info() has a TOCTOU race between two passes over the block group RAID type lists. The first pass counts entries to determine the allocation size, then the second pass fills the buffer. The groups_sem rwlock is released between passes, allowing concurrent block group removal to reduce the entry count. When the second pass fills fewer entries than the first pass counted, copy_to_user() copies the full alloc_size bytes including trailing uninitialized kmalloc bytes to userspace. Fix by copying only total_spaces entries (the actually-filled count from the second pass) instead of alloc_size bytes, and switch to kzalloc so any future copy size mismatch cannot leak heap data.

References

Community reviews

Loading reviews…