CVE-2024-56565: Linux kernel · f2fs: fix to drop all discards after creating snapshot on lvm device
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 30 Oct 2026, 14:33 UTC
Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
AI-suggested
A patch has been applied to the Linux kernel to fix this issue by dropping remaining discard commands after snapshot creation and validating discard_max_bytes before issuing discard commands. Users should update to the fixed kernel versions once available. No other mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's f2fs filesystem was fixed to prevent kernel panic caused by improper handling of discard commands after creating a snapshot on an LVM device. The issue occurs because discard_max_bytes is set to zero after snapshot creation, leading to a NULL bio pointer and kernel panic when discard commands are submitted.
References
- git.kernel.org/stable/c/0f3b00763dae90e94eed94a39d32d252d8750e9d (opens in a new tab)
- git.kernel.org/stable/c/ed24ab98242f8d22b66fbe0452c97751b5ea4e22 (opens in a new tab)
- git.kernel.org/stable/c/15136c3861a3341db261ebdbb6ae4ae1765635e2 (opens in a new tab)
- git.kernel.org/stable/c/bc8aeb04fd80cb8cfae3058445c84410fd0beb5e (opens in a new tab)