CVE-2024-56619

nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry()

HIGH
7.8
CVSS Score
Published: December 27, 2024 at 02:51 PM UTC
Updated: August 5, 2026 at 12:44 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential out-of-bounds memory access in nilfs_find_entry() Syzbot reported that when searching for records in a directory where the inode's i_size is corrupted and has a large value, memory access outside the folio/page range may occur, or a use-after-free bug may be detected if KASAN is enabled. This is because nilfs_last_byte(), which is called by nilfs_find_entry() and others to calculate the number of valid bytes of directory data in a page from i_size and the page index, loses the upper 32 bits of the 64-bit size information due to an inappropriate type of local variable to which the i_size value is assigned. This caused a large byte offset value due to underflow in the end address calculation in the calling nilfs_find_entry(), resulting in memory access that exceeds the folio/page size. Fix this issue by changing the type of the local variable causing the bit loss from "unsigned int" to "u64". The return value of nilfs_last_byte() is also of type "unsigned int", but it is truncated so as not to exceed PAGE_SIZE and no bit loss occurs, so no change is required.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.30 ≤ v < 5.10.2312.6.30 ≤ v < 5.15.1742.6.30 ≤ v < 5.4.2872.6.30 ≤ v < 6.1.1202.6.30 ≤ v < 6.12.52.6.30 ≤ v < 6.132.6.30 ≤ v < 6.6.665.11 ≤ v < 5.15.1745.16 ≤ v < 6.1.1205.5 ≤ v < 5.10.2316.2 ≤ v ≤ 6.6.666.7 ≤ v ≤ 6.12.52ba466d74ed74f073257f86e61519cb8f8f461846.13 rc1
Vendor states this is fixed in 09d6d05579fd46e61abf6e457bb100ff11f3a9d3 (fixed)
Vendor states this is fixed in 31f7b57a77d4c82a34ddcb6ff35b5aa577ef153e (fixed)
Vendor states this is fixed in 48eb6e7404948032bbe811c5affbe39f6b316951 (fixed)
Vendor states this is fixed in 5af8366625182f01f6d8465c9a3210574673af57 (fixed)
Vendor states this is fixed in 985ebec4ab0a28bb5910c3b1481a40fbf7f9e61d (fixed)
Vendor states this is fixed in c3afea07477baccdbdec4483f8d5e59d42a3f67f (fixed)
Vendor states this is fixed in e3732102a9d638d8627d14fdf7b208462f0520e0 (fixed)
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 5.10.231 (unaffected)
Vendor states this is fixed in 5.15.174 (unaffected)
Vendor states this is fixed in 5.4.287 (unaffected)
Vendor states this is fixed in 6.1.120 (unaffected)
Vendor states this is fixed in 6.12.5 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.66 (unaffected)

References (9)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/09d6d05579fd46e61abf6e457bb100ff11f3a9d3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/31f7b57a77d4c82a34ddcb6ff35b5aa577ef153e
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/48eb6e7404948032bbe811c5affbe39f6b316951
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5af8366625182f01f6d8465c9a3210574673af57
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/985ebec4ab0a28bb5910c3b1481a40fbf7f9e61d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c3afea07477baccdbdec4483f8d5e59d42a3f67f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e3732102a9d638d8627d14fdf7b208462f0520e0
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card