{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50303 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-50303 is a medium-severity memory corruption vulnerability in Linux kernel, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-50303 and fix it if it is affected.\n\nWhat it is: CVE-2024-50303 is a medium-severity memory corruption vulnerability in Linux kernel, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-50303 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-50303/ (Markdown: https://insights.sbomify.com/CVE-2024-50303/index.md)","id":"CVE-2024-50303","markdown":"https://insights.sbomify.com/CVE-2024-50303/index.md","name":"CVE-2024-50303","record":{"aliases":["BELL-CVE-2024-50303","DEBIAN-CVE-2024-50303","GHSA-p747-x98p-7r7q","UBUNTU-CVE-2024-50303"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel kexec subsystem causes crashes when using CXL memory expanders with IMA enabled, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nresource,kexec: walk_system_ram_res_rev must retain resource flags\n\nwalk_system_ram_res_rev() erroneously discards resource flags when passing\nthe information to the callback.\n\nThis causes systems with IORESOURCE_SYSRAM_DRIVER_MANAGED memory to have\nthese resources selected during kexec to store kexec buffers if that\nmemory happens to be at placed above normal system ram.\n\nThis leads to undefined behavior after reboot.  If the kexec buffer is\nnever touched, nothing happens.  If the kexec buffer is touched, it could\nlead to a crash (like below) or undefined behavior.\n\nTested on a system with CXL memory expanders with driver managed memory,\nTPM enabled, and CONFIG_IMA_KEXEC=y.  Adding printk's showed the flags\nwere being discarded and as a result the check for\nIORESOURCE_SYSRAM_DRIVER_MANAGED passes.\n\nfind_next_iomem_res: name(System RAM (kmem))\n\t\t     start(10000000000)\n\t\t     end(1034fffffff)\n\t\t     flags(83000200)\n\nlocate_mem_hole_top_down: start(10000000000) end(1034fffffff) flags(0)\n\n[.] BUG: unable to handle page fault for address: ffff89834ffff000\n[.] #PF: supervisor read access in kernel mode\n[.] #PF: error_code(0x0000) - not-present page\n[.] PGD c04c8bf067 P4D c04c8bf067 PUD c04c8be067 PMD 0\n[.] Oops: 0000 [#1] SMP\n[.] RIP: 0010:ima_restore_measurement_list+0x95/0x4b0\n[.] RSP: 0018:ffffc900000d3a80 EFLAGS: 00010286\n[.] RAX: 0000000000001000 RBX: 0000000000000000 RCX: ffff89834ffff000\n[.] RDX: 0000000000000018 RSI: ffff89834ffff000 RDI: ffff89834ffff018\n[.] RBP: ffffc900000d3ba0 R08: 0000000000000020 R09: ffff888132b8a900\n[.] R10: 4000000000000000 R11: 000000003a616d69 R12: 0000000000000000\n[.] R13: ffffffff8404ac28 R14: 0000000000000000 R15: ffff89834ffff000\n[.] FS:  0000000000000000(0000) GS:ffff893d44640000(0000) knlGS:0000000000000000\n[.] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[.] ata5: SATA link down (SStatus 0 SControl 300)\n[.] CR2: ffff89834ffff000 CR3: 000001034d00f001 CR4: 0000000000770ef0\n[.] PKRU: 55555554\n[.] Call Trace:\n[.]  \u003cTASK\u003e\n[.]  ? __die+0x78/0xc0\n[.]  ? page_fault_oops+0x2a8/0x3a0\n[.]  ? exc_page_fault+0x84/0x130\n[.]  ? asm_exc_page_fault+0x22/0x30\n[.]  ? ima_restore_measurement_list+0x95/0x4b0\n[.]  ? template_desc_init_fields+0x317/0x410\n[.]  ? crypto_alloc_tfm_node+0x9c/0xc0\n[.]  ? init_ima_lsm+0x30/0x30\n[.]  ima_load_kexec_buffer+0x72/0xa0\n[.]  ima_init+0x44/0xa0\n[.]  __initstub__kmod_ima__373_1201_init_ima7+0x1e/0xb0\n[.]  ? init_ima_lsm+0x30/0x30\n[.]  do_one_initcall+0xad/0x200\n[.]  ? idr_alloc_cyclic+0xaa/0x110\n[.]  ? new_slab+0x12c/0x420\n[.]  ? new_slab+0x12c/0x420\n[.]  ? number+0x12a/0x430\n[.]  ? sysvec_apic_timer_interrupt+0xa/0x80\n[.]  ? asm_sysvec_apic_timer_interrupt+0x16/0x20\n[.]  ? parse_args+0xd4/0x380\n[.]  ? parse_args+0x14b/0x380\n[.]  kernel_init_freeable+0x1c1/0x2b0\n[.]  ? rest_init+0xb0/0xb0\n[.]  kernel_init+0x16/0x1a0\n[.]  ret_from_fork+0x2f/0x40\n[.]  ? rest_init+0xb0/0xb0\n[.]  ret_from_fork_asm+0x11/0x20\n[.]  \u003c/TASK\u003e","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"resource,kexec: walk_system_ram_res_rev must retain resource flags","id":"CVE-2024-50303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find()","id":"CVE-2024-50304"},"packages":[],"prev":{"headline":"Linux Kernel Use of Uninitialized Resource","id":"CVE-2024-50302"},"products":["Linux"],"published":"2024-11-19","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A flaw in the Linux kernel kexec subsystem causes crashes when using CXL memory expanders with IMA enabled, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2024-50303/"}