Answer in brief
CVE-2026-46159 records a Medium severity (CVSS 4.7) vulnerability in btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46159 records a Medium severity (CVSS 4.7) vulnerability in btrfs: fix btrfs_ioctl_space_info() slot_count TOCTOU which can lead to info-leak. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <f407aad350bdea4db300c47433573b7a41630d33 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d8224b1be6627c6c3b204bfb264508d27c65ac44 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d69a4a6813fdba7c4cc3695a7e843842b240790d || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <f5ee467b56764964027c361641f64953fc0f8f9a || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <4fdc6ee0802121d9cd96b8d085e589f51e5a4ec3 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <5d12e0ab009ade48c1bff9324fd9bea2c773d088 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d09d67d5de577cedae3de9497dff217e0ac8b641 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <973e57c726c1f8e77259d1c8e519519f1e9aea77 | f407aad350bdea4db300c47433573b7a41630d33, d8224b1be6627c6c3b204bfb264508d27c65ac44, d69a4a6813fdba7c4cc3695a7e843842b240790d, f5ee467b56764964027c361641f64953fc0f8f9a, 4fdc6ee0802121d9cd96b8d085e589f51e5a4ec3, 5d12e0ab009ade48c1bff9324fd9bea2c773d088, d09d67d5de577cedae3de9497dff217e0ac8b641, 973e57c726c1f8e77259d1c8e519519f1e9aea77 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 4.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <f407aad350bdea4db300c47433573b7a41630d33 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d8224b1be6627c6c3b204bfb264508d27c65ac44 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d69a4a6813fdba7c4cc3695a7e843842b240790d || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <f5ee467b56764964027c361641f64953fc0f8f9a || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <4fdc6ee0802121d9cd96b8d085e589f51e5a4ec3 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <5d12e0ab009ade48c1bff9324fd9bea2c773d088 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <d09d67d5de577cedae3de9497dff217e0ac8b641 || >=7fde62bffb576d384ea49a3aed3403d5609ee5bc <973e57c726c1f8e77259d1c8e519519f1e9aea77 | f407aad350bdea4db300c47433573b7a41630d33, d8224b1be6627c6c3b204bfb264508d27c65ac44, d69a4a6813fdba7c4cc3695a7e843842b240790d, f5ee467b56764964027c361641f64953fc0f8f9a, 4fdc6ee0802121d9cd96b8d085e589f51e5a4ec3, 5d12e0ab009ade48c1bff9324fd9bea2c773d088, d09d67d5de577cedae3de9497dff217e0ac8b641, 973e57c726c1f8e77259d1c8e519519f1e9aea77 |
| Linux/Linuxgeneric | 2.6.34 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.