CVE-2024-53141

Published Dec 6, 2024

Last updated 9 months ago

CVSS high 7.8
Linux Kernel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2024-53141 is a vulnerability in the Linux kernel's netfilter subsystem, specifically within the ipset component. The flaw stems from a missing range check in the `bitmap_ip_uadt` function when handling `IPSET_ATTR_CIDR` parameters. The vulnerability occurs when `tb[IPSET_ATTR_IP_TO]` is absent, but `tb[IPSET_ATTR_CIDR]` is present, causing the `ip` and `ip_to` values to be swapped. This oversight leads to an out-of-bounds memory access, potentially allowing attackers to manipulate memory outside the intended boundaries.

Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: add missing range check in bitmap_ip_uadt When tb[IPSET_ATTR_IP_TO] is not present but tb[IPSET_ATTR_CIDR] exists, the values of ip and ip_to are slightly swapped. Therefore, the range check for ip should be done later, but this part is missing and it seems that the vulnerability occurs. So we should add missing range checks and remove unnecessary range checks.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel

Risk scores

CVSS 3.1

Type
Primary
Base score
7.8
Impact score
5.9
Exploitability score
1.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
NVD-CWE-noinfo

Social media

Hype score
Not currently trending
  1. Top 5 Trending CVEs: 1 - CVE-2026-5426 2 - CVE-2023-29218 3 - CVE-2026-2031 4 - CVE-2026-41096 5 - CVE-2024-53141 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    26 May 2026

    145 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  2. Critical #SUSE Linux Kernel Security Update. We've detailed the newly disclosed netfilter vulnerability (CVE-2024-53141). Read more: 👉 https://t.co/yIUqeqCbxm #Security https://t.co/61v72Ku3Hh

    @Cezar_H_Linux

    24 Nov 2025

    37 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. به تازگی آسیب پذیری جدیدی با کد شناسایی CVE-2024-53141 برای کرنل های لینوکس تا نسخه 16.12.2 از نوع privilege escalation منتشر شده است.‌برای پیشگیری و مقابله با این تهدید ، کرن

    @AmirHossein_sec

    20 Aug 2025

    28 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  4. CVE-2024-53141: Root-Level Escalation in Linux Netfilter #Security #Linux https://t.co/wGkxPYZvmN

    @gnoppixlinux

    20 Aug 2025

    18 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  5. Curious how a bug in Linux’s ipset subsystem could lead to full kernel compromise? In our new article, we revisit CVE-2024-53141 to break down the bug, explore the memory layout, and show how it can be turned into a powerful privilege escalation.

    @SecuriTeam_SSD

    11 Aug 2025

    43751 Impressions

    4 Retweets

    33 Likes

    42 Bookmarks

    0 Replies

    1 Quote

  6. Curious how a bug in Linux’s ipset subsystem could lead to full kernel compromise? In our new article, we revisit CVE-2024-53141 to break down the bug, explore the memory layout, and show how it can be turned into a powerful privilege escalation.

    @SecuriTeam_SSD

    11 Aug 2025

    60089 Impressions

    3 Retweets

    29 Likes

    30 Bookmarks

    0 Replies

    0 Quotes

  7. Curious how a bug in Linux’s ipset subsystem could lead to full kernel compromise? In our new article, we revisit CVE-2024-53141 to break down the bug, explore the memory layout, and show how it can be turned into a powerful privilege escalation. Read it here:

    @SecuriTeam_SSD

    11 Aug 2025

    1192 Impressions

    3 Retweets

    10 Likes

    7 Bookmarks

    0 Replies

    0 Quotes

  8. oof! CVE-2024-53141 linux Kernel Flaw Enables Privilege Escalation мяу!, я кот>.< https://t.co/Y7N9QTrq0v

    @assadKEK

    13 Jun 2025

    5 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. Linux kernel Netfiler Ipset exploitation (CVE-2024-53141) https://t.co/jBX50HbsEu #infosec #Linux https://t.co/aihiBfaUSG

    @0xor0ne

    24 Apr 2025

    2802 Impressions

    12 Retweets

    82 Likes

    40 Bookmarks

    0 Replies

    0 Quotes

  10. 🚨 New Linux Kernel 0-Day Alert 🚨​ CVE-2024-53141: A critical flaw in the Linux kernel's IP sets framework allows local attackers to escalate privileges and potentially gain root access.​Cyber Security News 🔍 Vulnerability Details: Affected Component: IP sets framework in the

    @CareWeDoNot

    18 Apr 2025

    48 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  11. security-research/pocs/linux/kernelctf/CVE-2024-53141_lts/exploit/lts-6.6.62 at master · google/security-research · GitHub https://t.co/RF96paZJ4o

    @akaclandestine

    18 Apr 2025

    596 Impressions

    0 Retweets

    1 Like

    4 Bookmarks

    0 Replies

    0 Quotes

  12. Critical Linux Kernel Flaw CVE-2024-53141: High-Risk Privilege Escalation Uncovered Read the full story: https://t.co/8oLIat6pFz

    @theinfosecnews

    18 Apr 2025

    19 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  13. CVE-2024-53141: Linux Kernel Flaw Enables Privilege Escalation, PoC Releases https://t.co/ylBgo8KoXp

    @Dinosn

    18 Apr 2025

    2143 Impressions

    4 Retweets

    30 Likes

    13 Bookmarks

    0 Replies

    0 Quotes

  14. Linuxカーネルの権限昇格脆弱性CVE-2024-53141に対応するPoC(攻撃の概念実証コード)が公表された。netfilterサブシステムのipsetコンポーネントにおける境界外アクセスの脆弱性で、KASLRを迂回しカーネルレベルのコード実行が可能。 https://t.co/ObCm4VhV3j

    @__kokumoto

    18 Apr 2025

    2577 Impressions

    15 Retweets

    38 Likes

    15 Bookmarks

    0 Replies

    0 Quotes

  15. Linuxカーネルの脆弱性CVE-2024-53141が公開された。PoCもGithubに公開済み。この欠陥はnetfilterサブシステムのipsetコンポーネントに存在し、深刻なOOB(Out-of-Bounds)アクセスを引き起こす。

    @yousukezan

    18 Apr 2025

    776 Impressions

    0 Retweets

    6 Likes

    3 Bookmarks

    0 Replies

    0 Quotes

  16. CVE-2024-53141: Linux Kernel Flaw Enables Privilege Escalation, PoC Releases A vulnerability (CVE-2024-53141) in the Linux kernel's ipset component allows for privilege escalation and kernel-level code execution. https://t.co/g97ZL1CJh3

    @Daily_CyberSec

    18 Apr 2025

    2629 Impressions

    19 Retweets

    48 Likes

    16 Bookmarks

    0 Replies

    0 Quotes

  17. CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt https://t.co/ZalPG49kRS I have completed writing a PoC that successfully LPE using my vulnerability :) https://t.co/gHcWH9jMlg

    @aha310510

    18 Jan 2025

    49 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  18. CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt https://t.co/ZalPG49kRS https://t.co/o6yqb5XJDp

    @aha310510

    18 Jan 2025

    5 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  19. New post from https://t.co/uXvPWJy6tj (CVE-2024-53141 | Linux Kernel up to 4.19.324/6.11.10/6.12.1 netfilter bitmap_ip_uadt Privilege Escalation (Nessus ID 214250)) has been published on https://t.co/qysxIKqqKv

    @WolfgangSesin

    16 Jan 2025

    14 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  20. #exploit 1. CVE-2023-6932, CVE-2023-0461: UaF/LPE in Linux kernel https://t.co/OOfZ4dy95Q 2. CVE-2024-53141: An OOB Write Vulnerability in Netfiler Ipset https://t.co/rVzuElL9KO 3. CVE-2024-50603: Aviatrix Network Controller Command Injection Vulnerability… https://t.co/s0jItYw

    @ksg93rd

    9 Jan 2025

    62 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  21. CVE-2024-53141 (CVSS:7.8, HIGH) is Analyzed. In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: add missing range check in bitmap..https://t.co/eL4jWyuse9 #cybersecurityawareness #cybersecurity #CVE #infosec #hacker #nvd #mitre

    @cracbot

    11 Dec 2024

    6 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  22. CVE-2024-53141 In the Linux kernel, the following vulnerability has been resolved: netfilter: ipset: add missing range check in bitmap_ip_uadt When tb[IPSET_ATTR_IP_TO] is not pre… https://t.co/GJo7s2Y0N0

    @CVEnew

    6 Dec 2024

    332 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level When recovering hugepages in the shadow MMU, verify that the base gfn of the shadow page is actually contained within the target memslot, *before* querying the max mapping level given the shadow page's gfn. Failure to pre-check the validity of the gfn can lead to an out-of-bounds access to the slot's lpage_info (which typically manifests as a host #PF because the lpage_info is vmalloc'd) if the guest creates a hugepage mapping (in its PTEs) that extends "below" the bounds of a memslot. When faulting in memory for a guest, and the size of the guest mapping is greater than KVM's (current) max mapping, then KVM will create a "direct" shadow page (direct in that there are no gPTEs to shadow, and so the target gfn is a direct calculation given the base gfn of the shadow page). The hugepage recovery flow looks for such direct shadow pages, as forcing 4KiB mappings when dirty logging generates the guest > host mapping size case. When the 4KiB restriction is lifted, then KVM can replace the shadow page with a hugepage. But if KVM originally used a smaller mapping than the guest because the range of memory covered by the guest hugepage exceeds the bounds of a memslot, then KVM will link a direct shadow page with a gfn that is outside the bounds of the memslot being used to fault in memory. The rmap entry added for the leaf mapping is correct and within bounds, but the gfn of the leaf SPTE's parent shadow page will be out of bounds. BUG: unable to handle page fault for address: ffffc90000806ffc #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 100000067 P4D 100000067 PUD 1002a7067 PMD 10612f067 PTE 0 Oops: Oops: 0000 [#1] SMP CPU: 13 UID: 1000 PID: 757 Comm: mmu_stress_test Not tainted 7.1.0-rc1-48ce1e26eace-x86_pir_to_irr_comments-vm #341 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:kvm_mmu_max_mapping_level+0x79/0x2b0 [kvm] Call Trace: <TASK> kvm_mmu_recover_huge_pages+0x21b/0x320 [kvm] kvm_set_memslot+0x1ee/0x590 [kvm] kvm_set_memory_region.part.0+0x3a1/0x4d0 [kvm] kvm_vm_ioctl+0x9bf/0x15d0 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0xbb0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f21c0f1a9bf </TASK> Don't bother pre-checking the bounds of the potential hugepage, i.e. don't check that e.g. sp->gfn + KVM_PAGES_PER_HPAGE(sp->role.level + 1) is also within the memslot, as the checks performed by kvm_mmu_max_mapping_level() are a superset of the basic bounds checks. I.e. pre-checking the full range would be a dubious micro-optimization.CVE-2026-63807
  2. In the Linux kernel, the following vulnerability has been resolved: KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() Drop a BUG_ON() that has been reachable since it was first added, way back in 2009, and instead use get_unaligned() to perform potentially-unaligned accesses. For a given store, KVM x86's emulator tracks the entire value in the destination operand, x86_emulate_ctxt.dst. If the destination is memory, and the target splits multiple pages and/or is emulated MMIO, then KVM handles each fragment independently. E.g. on a page split starting at page offset 0xffc, KVM writes 4 bytes to the first page, then the remaining bytes to the second page, using ctxt->dst as the source for both (with appropriate offsets). If the destination splits a page *and* hits emulated MMIO on the second page, then KVM will complete the write to the first page, then emulate the MMIO access to the second page. If there is a datamatch-enabled ioeventfd at offset 0 of the second page, then KVM will process the remainder of the store as a potential ioeventfd signal. Putting it all together, if the guest emits a store that splits a page starting at page offset N, and the second page has a datamatch-enabled ioeventfd at offset 0, then KVM will check for datamatch using &dst.valptr[N] as the source. Due to dst (and thus dst.valptr) being 32-byte aligned, if N is not aligned to @len, the BUG_ON() fires. E.g. with a 16-byte store at page offset 0xffc, to an ioeventfd of len 8, all initial checks in ioeventfd_in_range() will succeed, and the BUG_ON() fires due to @val being 4-byte aligned, but not 8-byte aligned. ------------[ cut here ]------------ kernel BUG at arch/x86/kvm/../../../virt/kvm/eventfd.c:783! Oops: invalid opcode: 0000 [#1] SMP CPU: 0 UID: 1000 PID: 615 Comm: repro Not tainted 7.1.0-rc2-ff238429d1ea #365 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:ioeventfd_write+0x6c/0x70 [kvm] Call Trace: <TASK> __kvm_io_bus_write+0x85/0xb0 [kvm] kvm_io_bus_write+0x53/0x80 [kvm] vcpu_mmio_write+0x66/0xf0 [kvm] emulator_read_write_onepage+0x12a/0x540 [kvm] emulator_read_write+0x109/0x2b0 [kvm] x86_emulate_insn+0x4f8/0xfb0 [kvm] x86_emulate_instruction+0x181/0x790 [kvm] kvm_mmu_page_fault+0x313/0x630 [kvm] vmx_handle_exit+0x18a/0x590 [kvm_intel] kvm_arch_vcpu_ioctl_run+0xc81/0x1c90 [kvm] kvm_vcpu_ioctl+0x2d5/0x970 [kvm] __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0xb7/0x890 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f19c931a9bf </TASK> Modules linked in: kvm_intel kvm irqbypass ---[ end trace 0000000000000000 ]--- In a perfect world, the fix would be to simply delete the BUG_ON(), as KVM x86 doesn't perform alignment checks on "normal" memory accesses at CPL0. Sadly, C99 ruins all the fun; while the x86 architecture plays nice, dereferencing an unaligned pointer directly is undefined behavior in C, e.g. triggers splats when running with CONFIG_UBSAN_ALIGNMENT=y.CVE-2026-63806
  3. In the Linux kernel, the following vulnerability has been resolved: hdlc_ppp: sync per-proto timers before freeing hdlc state Each PPP control protocol (LCP/IPCP/IPV6CP) embedded in struct ppp registers a timer via timer_setup(). That struct ppp is the hdlc->state allocation, which detach_hdlc_protocol() frees with kfree() in both teardown paths: unregister_hdlc_device() and the re-attach inside attach_hdlc_protocol(). The ppp proto never registered a .detach callback, so detach_hdlc_protocol() performs no timer synchronization before the kfree(). The only cancel, timer_delete(&proto->timer) in ppp_cp_event(), is partial (it does not wait for a running callback) and only runs on the ->CLOSED transition; ppp_stop()/ppp_close() do not sync either. A ppp_timer callback already executing (blocked on ppp->lock) survives the kfree and then dereferences proto->state / ppp->lock in freed memory, leading to a use-after-free. Fix this by adding a .detach helper that calls timer_shutdown_sync() on every per-proto timer. detach_hdlc_protocol() invokes proto->detach(dev) before kfree(hdlc->state), so timer_shutdown_sync() now runs on both free paths. timer_shutdown_sync() is used instead of timer_delete_sync() because the keepalive path re-arms the timer through add_timer()/mod_timer() and shutdown blocks any re-activation during teardown. Initialize the per-protocol timers in ppp_ioctl() when the protocol is attached, and remove the now-redundant timer_setup() from ppp_start(), so that the timers are initialized exactly once at attach time and ppp_timer_release() never operates on uninitialized timer_list structures. attach_hdlc_protocol() uses kmalloc() (not kzalloc), so struct ppp's protos[i].timer is uninitialized garbage until the first timer_setup(); without this init-at-attach, attaching the PPP protocol without ever bringing the device up would leave timer_shutdown_sync() operating on uninitialized memory in .detach. Moving the init out of ppp_start() (which only runs on NETDEV_UP) into the attach path makes the initialization unconditional and avoids initializing the same timer_list twice. This bug was found by static analysis.CVE-2026-63803