high CVSS 7.1

CVE-2024-53147·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: exfat: fix out-of-bounds access of directory entries In the case of the directory size is greater than or equal to the cluster size, if start_clu becomes an EOF cluster(an invalid cluster) due to file system corruption, then the directory entry where ei->hint_femp.eidx hint is outside the directory, resulting in an out-of-bounds access, which may cause further file system corruption. This commit adds a check for start_clu, if it is an invalid cluster, the file or directory will be treated as empty.

Severity
high
Software
Kernel
Fixed in
6.12.2
Published
2024-12-24

Affected versions

From: 6.12

Until: 6.12.2

Fixed in: 6.12.2

How to fix this CVE

Update your Linux kernel to version 6.12.2 or later to patch an out-of-bounds memory access vulnerability in the exFAT filesystem driver. This vulnerability could allow local attackers with filesystem access to trigger kernel memory corruption through a malformed exFAT partition. Apply the kernel update and reboot your system to ensure the fix is active.

sudo dnf update kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your kernel version with `uname -r` and compare against 6.12.2. Versions 6.12.0, 6.12.1, or 6.12.2 are affected if below 6.12.2.
  2. Step 2: Verify if exFAT filesystems are mounted on your system by running `mount | grep exfat` or `lsblk -f | grep exfat`.
  3. Step 3: Search kernel logs for exFAT-related errors using `dmesg | grep -i exfat` or `journalctl -u kernel | grep -i exfat` to identify potential exploitation attempts.
  4. Step 4: After patching, confirm the kernel update with `uname -r` shows version 6.12.2 or higher, and verify with `dmesg | head -20` that the system booted the new kernel.

FAQ

What is CVE-2024-53147?

CVE-2024-53147 is a memory safety vulnerability in the Linux kernel's exFAT filesystem driver where corrupted filesystem metadata can cause the driver to access memory locations outside the bounds of a directory entry, potentially corrupting kernel memory and leading to system instability or privilege escalation.

Is CVE-2024-53147 being actively exploited?

No, CVE-2024-53147 is not listed as actively exploited by CISA and no public exploits are currently available. However, the vulnerability is locally exploitable and should still be patched promptly.

What versions of Kernel are affected by CVE-2024-53147?

Linux kernel versions 6.12.0, 6.12.1, and 6.12.2 (up to but not including the fixed 6.12.2) are affected. The vulnerability was introduced in the 6.12 series.

How do I check if my server is vulnerable to CVE-2024-53147?

Run `uname -r` to check your kernel version. If it shows 6.12.0 or 6.12.1, your system is vulnerable. Additionally, verify if exFAT partitions are mounted with `mount | grep exfat` to determine exposure.

Does Defensia detect CVE-2024-53147?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-53147 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-43501CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows ipv6_rpl_srh_rcv() decompresses an RFC 6554 Source Routing Header, swaps the next segment into ipv6_hdr->daddr, recompresses, then pulls the old header and pushes the new one plus the IPv6 header back. The recompressed header can be larger than the received one when the swap reduces the common-prefix length the segments share with daddr (CmprI=0, CmprE>0, seg[0][0] != daddr[0] gives the maximum +8 bytes). pskb_expand_head() was gated on segments_left == 0, so on earlier segments the push consumed unchecked headroom. Once skb_push() leaves fewer than skb->mac_len bytes in front of data, skb_mac_header_rebuild()'s call to: skb_set_mac_header(skb, -skb->mac_len); will store (data - head) - mac_len into the u16 mac_header field, which wraps to ~65530, and the following memmove() writes mac_len bytes ~64KiB past skb->head. A single AF_INET6/SOCK_RAW/IPV6_HDRINCL packet over lo with a two segment type-3 SRH (CmprI=0, CmprE=15) reaches headroom 8 after one pass; KASAN reports a 14-byte OOB write in ipv6_rthdr_rcv. Fix this by expanding the head whenever the remaining room is less than the push size plus mac_len, and request that much extra so the rebuilt MAC header fits afterwards.
CVE-2026-64385CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_ioctl() replay A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_ioctl_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.
CVE-2026-64391CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ksmbd: use opener credentials for ADS I/O Alternate data streams are stored as xattrs. Unlike regular file I/O, their read and write paths therefore call VFS xattr helpers which recheck inode permissions and LSM policy using the current task credentials. Run ADS I/O with the credentials captured when the SMB handle was opened.
CVE-2026-64383CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
CVE-2026-53176CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN In drivers/infiniband/ulp/isert/ib_isert.c, isert_login_recv_done() computes the login request payload length as wc->byte_len minus ISER_HEADERS_LEN with no lower bound, and login_req_len is a signed int. A remote iSER initiator can post a login Send work request carrying fewer than ISER_HEADERS_LEN (76) bytes, so the subtraction underflows and login_req_len becomes negative. isert_rx_login_req() then reads that negative length back into a signed int, takes size = min(rx_buflen, MAX_KEY_VALUE_PAIRS), and because the min() is signed it keeps the negative value; the value is then passed as the memcpy() length and sign-extended to a multi-gigabyte size_t. The copy into the 8192-byte login->req_buf runs far out of bounds and faults, crashing the target node. The login phase precedes iSCSI authentication, so no credentials are required to reach this path. Reject any login PDU shorter than ISER_HEADERS_LEN before the subtraction, mirroring the existing early return on a failed work completion, so login_req_len can never go negative. The upper bound was already safe: a posted login buffer cannot deliver more than ISER_RX_PAYLOAD_SIZE, so the difference stays at or below MAX_KEY_VALUE_PAIRS and the existing min() clamps it; only the missing lower bound needs to be added.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-53147. Free for 1 server.

Get started free