{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53419 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53419 is a medium-severity vulnerability in Linux kernel, published on 18 Sep 2025. 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-2023-53419 and fix it if it is affected.\n\nWhat it is: CVE-2023-53419 is a medium-severity vulnerability in Linux kernel, published on 18 Sep 2025. 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-2023-53419 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-2023-53419/ (Markdown: https://insights.sbomify.com/CVE-2023-53419/index.md)","id":"CVE-2023-53419","markdown":"https://insights.sbomify.com/CVE-2023-53419/index.md","name":"CVE-2023-53419","record":{"aliases":["BELL-CVE-2023-53419","DEBIAN-CVE-2023-53419","GHSA-w2v8-x9hv-74wh","UBUNTU-CVE-2023-53419"],"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 race condition in the Linux kernel RCU subsystem can cause a NULL pointer dereference, leading to a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nrcu: Protect rcu_print_task_exp_stall() -\u003eexp_tasks access\n\nFor kernels built with CONFIG_PREEMPT_RCU=y, the following scenario can\nresult in a NULL-pointer dereference:\n\n           CPU1                                           CPU2\nrcu_preempt_deferred_qs_irqrestore                rcu_print_task_exp_stall\n  if (special.b.blocked)                            READ_ONCE(rnp-\u003eexp_tasks) != NULL\n    raw_spin_lock_rcu_node\n    np = rcu_next_node_entry(t, rnp)\n    if (\u0026t-\u003ercu_node_entry == rnp-\u003eexp_tasks)\n      WRITE_ONCE(rnp-\u003eexp_tasks, np)\n      ....\n      raw_spin_unlock_irqrestore_rcu_node\n                                                    raw_spin_lock_irqsave_rcu_node\n                                                    t = list_entry(rnp-\u003eexp_tasks-\u003eprev,\n                                                        struct task_struct, rcu_node_entry)\n                                                    (if rnp-\u003eexp_tasks is NULL, this\n                                                       will dereference a NULL pointer)\n\nThe problem is that CPU2 accesses the rcu_node structure's-\u003eexp_tasks\nfield without holding the rcu_node structure's -\u003elock and CPU2 did\nnot observe CPU1's change to rcu_node structure's -\u003eexp_tasks in time.\nTherefore, if CPU1 sets rcu_node structure's-\u003eexp_tasks pointer to NULL,\nthen CPU2 might dereference that NULL pointer.\n\nThis commit therefore holds the rcu_node structure's -\u003elock while\naccessing that structure's-\u003eexp_tasks field.\n\n[ paulmck: Apply Frederic Weisbecker feedback. ]","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":"rcu: Protect rcu_print_task_exp_stall() -\u003eexp_tasks access","id":"CVE-2023-53419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":5,"next":{"headline":"ntfs: Fix panic about slab-out-of-bounds caused by ntfs_listxattr()","id":"CVE-2023-53420"},"packages":[],"prev":{"headline":"USB: gadget: lpc32xx_udc: fix memory leak with using debugfs_lookup()","id":"CVE-2023-53418"},"products":["Linux"],"published":"2025-09-18","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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 race condition in the Linux kernel RCU subsystem can cause a NULL pointer dereference, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2023-53419/"}