Loading vulnerability…
CVE-2024-26973 is an uninitialized-memory disclosure vulnerability in the Linux kernel FAT filesystem's fat_encode_fh_nostale() function. When encoding a file handle without a parent, the function initializes only 10 bytes. File-handle lengths must be multiples of four bytes, so the returned handle occupies 12 bytes, leaving its final two bytes uninitialized. Returning the handle to userspace can expose uninitialized kernel information. The fix initializes the full file-handle length.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An uninitialized-memory vulnerability in the Linux kernel FAT filesystem's fat_encode_fh_nostale() function. Encoding a file handle without a parent leaves two bytes uninitialized, potentially leaking kernel information to userspace. The fix initializes the full handle length. The advisory recommends updating the affected Google kernel packages to version 19165.0.0 or later.
Linux kernel FAT filesystem vulnerability involving an uninitialized nostale file-handle field.
Linux kernel FAT filesystem uninitialized nostale file-handle field flaw.
Linux kernel FAT filesystem uninitialized-field vulnerability in nostale file handles.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.