CVE-2026-99448: ufs: use u64 for directory size in ufs_last_byte

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ufs: use u64 for directory size in ufslastbyte

ufs1readinode() and ufs2readinode() copy the untrusted 64-bit on-disk size into inode->isize. ufslastbyte() then truncates that value to an unsigned int before calculating the valid extent of a directory folio.

A directory size of exactly 4 GiB is truncated to zero. In ufsfindentry(), subtracting the requested record length from that zero forms an endpoint almost 4 GiB beyond the mapped folio. A crafted UFS2 image produces:

BUG: KASAN: use-after-free in ufsfindentry+0x583/0x6e0 [ufs] Read of size 1 ... ufsfindentry ufsinodebyname ufslookup lookupslow pathlookupat

The KASAN classification reflects that the adjacent physical page was free; the source-level operation is an out-of-folio read. A controlled UFS1 test with CONFIGUFSFSWRITE enabled also made ufsfindentry() return a directory entry from an adjacent anonymous page. unlink() then passed that pointer to ufsdeleteentry(), which cleared the adjacent page's 3 2-bit dino. This write result reproduced three out of three times.

UFS normally requires a privileged mount path. A relevant boundary is a privileged automounter or image-processing service handling an attacker-supplied filesystem. The write primitive additionally requires UFS1 to be mounted read-write with CONFIGUFSFSWRITE enabled; the read is reachable with read-only UFS2.

Keep the intermediate size arithmetic at 64 bits so non-final pages are bounded at PAGESIZE. With this change, the same controlled tests reach the real on-disk directory entry and produce no adjacent-page write or KASAN report. A reproducer and full validation logs are available on request.

The vulnerable helper is present in v7.2-rc3, v7.1, v6.18.38, v6.12.95, v6.6.111, and upstream master at 1229e2e57a5c. Runtime reproduction and fix validation were performed in an x86-64 QEMU guest running v7.2-rc3 with generic KASAN.

Affected Software

7 affected componentsFixes available
linux/kernel>=2.6.18<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux*
debian/linux<6.12.117-1
6.12.117-1
debian/linux<7.3.3-1
7.3.3-1
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1
6.12.117-17.3.4-17.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1
  5. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.3-1
  6. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Event History

Nov 19, 2026
CVE Published
via MITRE·02:41 PM
Data Sourced
via MITRE·02:41 PM
Description
Data Sourced
via OSV·02:41 PM
DescriptionAffected Software
Data Sourced
via NVD·03:17 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203