{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-54322 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-54322 is a denial of service vulnerability in Linux, published on 30 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2023-54322 and fix it if it is affected.\n\nWhat it is: CVE-2023-54322 is a denial of service vulnerability in Linux, published on 30 Dec 2025. \nExploitation: There is no known exploitation of CVE-2023-54322 in the wild and no public exploit code.\n\nAffected product: Linux. 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-2023-54322/ (Markdown: https://insights.sbomify.com/CVE-2023-54322/index.md)","id":"CVE-2023-54322","markdown":"https://insights.sbomify.com/CVE-2023-54322/index.md","name":"CVE-2023-54322","record":{"aliases":["BELL-CVE-2023-54322","DEBIAN-CVE-2023-54322","GHSA-3rp4-j8x5-r3q5","ROOT-OS-DEBIAN-12-CVE-2023-54322","UBUNTU-CVE-2023-54322"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A flaw in the Linux kernel arm64 IRQ entry handling can cause excessive stack depot usage, leading to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: set __exception_irq_entry with __irq_entry as a default\n\nfilter_irq_stacks() is supposed to cut entries which are related irq entries\nfrom its call stack.\nAnd in_irqentry_text() which is called by filter_irq_stacks()\nuses __irqentry_text_start/end symbol to find irq entries in callstack.\n\nBut it doesn't work correctly as without \"CONFIG_FUNCTION_GRAPH_TRACER\",\narm64 kernel doesn't include gic_handle_irq which is entry point of arm64 irq\nbetween __irqentry_text_start and __irqentry_text_end as we discussed in below link.\nhttps://lore.kernel.org/all/CACT4Y+aReMGLYua2rCLHgFpS9io5cZC04Q8GLs-uNmrn1ezxYQ@mail.gmail.com/#t\n\nThis problem can makes unintentional deep call stack entries especially\nin KASAN enabled situation as below.\n\n[ 2479.383395]I[0:launcher-loader: 1719] Stack depot reached limit capacity\n[ 2479.383538]I[0:launcher-loader: 1719] WARNING: CPU: 0 PID: 1719 at lib/stackdepot.c:129 __stack_depot_save+0x464/0x46c\n[ 2479.385693]I[0:launcher-loader: 1719] pstate: 624000c5 (nZCv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--)\n[ 2479.385724]I[0:launcher-loader: 1719] pc : __stack_depot_save+0x464/0x46c\n[ 2479.385751]I[0:launcher-loader: 1719] lr : __stack_depot_save+0x460/0x46c\n[ 2479.385774]I[0:launcher-loader: 1719] sp : ffffffc0080073c0\n[ 2479.385793]I[0:launcher-loader: 1719] x29: ffffffc0080073e0 x28: ffffffd00b78a000 x27: 0000000000000000\n[ 2479.385839]I[0:launcher-loader: 1719] x26: 000000000004d1dd x25: ffffff891474f000 x24: 00000000ca64d1dd\n[ 2479.385882]I[0:launcher-loader: 1719] x23: 0000000000000200 x22: 0000000000000220 x21: 0000000000000040\n[ 2479.385925]I[0:launcher-loader: 1719] x20: ffffffc008007440 x19: 0000000000000000 x18: 0000000000000000\n[ 2479.385969]I[0:launcher-loader: 1719] x17: 2065726568207475 x16: 000000000000005e x15: 2d2d2d2d2d2d2d20\n[ 2479.386013]I[0:launcher-loader: 1719] x14: 5d39313731203a72 x13: 00000000002f6b30 x12: 00000000002f6af8\n[ 2479.386057]I[0:launcher-loader: 1719] x11: 00000000ffffffff x10: ffffffb90aacf000 x9 : e8a74a6c16008800\n[ 2479.386101]I[0:launcher-loader: 1719] x8 : e8a74a6c16008800 x7 : 00000000002f6b30 x6 : 00000000002f6af8\n[ 2479.386145]I[0:launcher-loader: 1719] x5 : ffffffc0080070c8 x4 : ffffffd00b192380 x3 : ffffffd0092b313c\n[ 2479.386189]I[0:launcher-loader: 1719] x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000022\n[ 2479.386231]I[0:launcher-loader: 1719] Call trace:\n[ 2479.386248]I[0:launcher-loader: 1719]  __stack_depot_save+0x464/0x46c\n[ 2479.386273]I[0:launcher-loader: 1719]  kasan_save_stack+0x58/0x70\n[ 2479.386303]I[0:launcher-loader: 1719]  save_stack_info+0x34/0x138\n[ 2479.386331]I[0:launcher-loader: 1719]  kasan_save_free_info+0x18/0x24\n[ 2479.386358]I[0:launcher-loader: 1719]  ____kasan_slab_free+0x16c/0x170\n[ 2479.386385]I[0:launcher-loader: 1719]  __kasan_slab_free+0x10/0x20\n[ 2479.386410]I[0:launcher-loader: 1719]  kmem_cache_free+0x238/0x53c\n[ 2479.386435]I[0:launcher-loader: 1719]  mempool_free_slab+0x1c/0x28\n[ 2479.386460]I[0:launcher-loader: 1719]  mempool_free+0x7c/0x1a0\n[ 2479.386484]I[0:launcher-loader: 1719]  bvec_free+0x34/0x80\n[ 2479.386514]I[0:launcher-loader: 1719]  bio_free+0x60/0x98\n[ 2479.386540]I[0:launcher-loader: 1719]  bio_put+0x50/0x21c\n[ 2479.386567]I[0:launcher-loader: 1719]  f2fs_write_end_io+0x4ac/0x4d0\n[ 2479.386594]I[0:launcher-loader: 1719]  bio_endio+0x2dc/0x300\n[ 2479.386622]I[0:launcher-loader: 1719]  __dm_io_complete+0x324/0x37c\n[ 2479.386650]I[0:launcher-loader: 1719]  dm_io_dec_pending+0x60/0xa4\n[ 2479.386676]I[0:launcher-loader: 1719]  clone_endio+0xf8/0x2f0\n[ 2479.386700]I[0:launcher-loader: 1719]  bio_endio+0x2dc/0x300\n[ 2479.386727]I[0:launcher-loader: 1719]  blk_update_request+0x258/0x63c\n[ 2479.386754]I[0:launcher-loader: 1719]  scsi_end_request+0x50/0x304\n[ 2479.386782]I[0:launcher-loader: 1719]  scsi_io_completion+0x88/0x160\n[ 2479.386808]I[0:launcher-loader: 1719]  scsi_finish_command+0x17c/0x194\n[ 2479.386833]I\n---truncated---","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":"arm64: set __exception_irq_entry with __irq_entry as a default","id":"CVE-2023-54322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"cxl/pmem: Fix nvdimm registration races","id":"CVE-2023-54323"},"packages":[],"prev":{"headline":"driver core: fix potential null-ptr-deref in device_add()","id":"CVE-2023-54321"},"products":["Linux"],"published":"2025-12-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-06-01","vendors":["Linux"]},"summary":"A flaw in the Linux kernel arm64 IRQ entry handling can cause excessive stack depot usage, leading to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2023-54322/"}