{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53345 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53345 is a medium-severity vulnerability in Linux kernel, published on 17 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-53345 and fix it if it is affected.\n\nWhat it is: CVE-2023-53345 is a medium-severity vulnerability in Linux kernel, published on 17 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-53345 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-53345/ (Markdown: https://insights.sbomify.com/CVE-2023-53345/index.md)","id":"CVE-2023-53345","markdown":"https://insights.sbomify.com/CVE-2023-53345/index.md","name":"CVE-2023-53345","record":{"aliases":["BELL-CVE-2023-53345","DEBIAN-CVE-2023-53345","GHSA-ggg7-h54g-wmq5","UBUNTU-CVE-2023-53345"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A data race in the Linux kernel's rxrpc module could lead to unexpected behavior or crashes during concurrent access.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":4.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: Fix potential data race in rxrpc_wait_to_be_connected()\n\nInside the loop in rxrpc_wait_to_be_connected() it checks call-\u003eerror to\nsee if it should exit the loop without first checking the call state.  This\nis probably safe as if call-\u003eerror is set, the call is dead anyway, but we\nshould probably wait for the call state to have been set to completion\nfirst, lest it cause surprise on the way out.\n\nFix this by only accessing call-\u003eerror if the call is complete.  We don't\nactually need to access the error inside the loop as we'll do that after.\n\nThis caused the following report:\n\n    BUG: KCSAN: data-race in rxrpc_send_data / rxrpc_set_call_completion\n\n    write to 0xffff888159cf3c50 of 4 bytes by task 25673 on cpu 1:\n     rxrpc_set_call_completion+0x71/0x1c0 net/rxrpc/call_state.c:22\n     rxrpc_send_data_packet+0xba9/0x1650 net/rxrpc/output.c:479\n     rxrpc_transmit_one+0x1e/0x130 net/rxrpc/output.c:714\n     rxrpc_decant_prepared_tx net/rxrpc/call_event.c:326 [inline]\n     rxrpc_transmit_some_data+0x496/0x600 net/rxrpc/call_event.c:350\n     rxrpc_input_call_event+0x564/0x1220 net/rxrpc/call_event.c:464\n     rxrpc_io_thread+0x307/0x1d80 net/rxrpc/io_thread.c:461\n     kthread+0x1ac/0x1e0 kernel/kthread.c:376\n     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308\n\n    read to 0xffff888159cf3c50 of 4 bytes by task 25672 on cpu 0:\n     rxrpc_send_data+0x29e/0x1950 net/rxrpc/sendmsg.c:296\n     rxrpc_do_sendmsg+0xb7a/0xc20 net/rxrpc/sendmsg.c:726\n     rxrpc_sendmsg+0x413/0x520 net/rxrpc/af_rxrpc.c:565\n     sock_sendmsg_nosec net/socket.c:724 [inline]\n     sock_sendmsg net/socket.c:747 [inline]\n     ____sys_sendmsg+0x375/0x4c0 net/socket.c:2501\n     ___sys_sendmsg net/socket.c:2555 [inline]\n     __sys_sendmmsg+0x263/0x500 net/socket.c:2641\n     __do_sys_sendmmsg net/socket.c:2670 [inline]\n     __se_sys_sendmmsg net/socket.c:2667 [inline]\n     __x64_sys_sendmmsg+0x57/0x60 net/socket.c:2667\n     do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n     do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80\n     entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\n    value changed: 0x00000000 -\u003e 0xffffffea","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":"rxrpc: Fix potential data race in rxrpc_wait_to_be_connected()","id":"CVE-2023-53345","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"kernel/fail_function: fix memory leak with using debugfs_lookup()","id":"CVE-2023-53346"},"packages":[],"prev":{"headline":"can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write","id":"CVE-2023-53344"},"products":["Linux"],"published":"2025-09-17","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 data race in the Linux kernel's rxrpc module could lead to unexpected behavior or crashes during concurrent access.","url":"https://insights.sbomify.com/CVE-2023-53345/"}