{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53703 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53703 is a vulnerability in Linux, published on 22 Oct 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-53703 and fix it if it is affected.\n\nWhat it is: CVE-2023-53703 is a vulnerability in Linux, published on 22 Oct 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-53703 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-53703/ (Markdown: https://insights.sbomify.com/CVE-2023-53703/index.md)","id":"CVE-2023-53703","markdown":"https://insights.sbomify.com/CVE-2023-53703/index.md","name":"CVE-2023-53703","record":{"aliases":["BELL-CVE-2023-53703","DEBIAN-CVE-2023-53703","GHSA-rmv6-m884-3827","UBUNTU-CVE-2023-53703"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A shift-out-of-bounds error in the AMD SFH HID driver can cause a kernel crash, requiring a patch to validate shift ranges.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\nHID: amd_sfh: Fix for shift-out-of-bounds\n\nShift operation of 'exp' and 'shift' variables exceeds the maximum number\nof shift values in the u32 range leading to UBSAN shift-out-of-bounds.\n\n...\n[    6.120512] UBSAN: shift-out-of-bounds in drivers/hid/amd-sfh-hid/sfh1_1/amd_sfh_desc.c:149:50\n[    6.120598] shift exponent 104 is too large for 64-bit type 'long unsigned int'\n[    6.120659] CPU: 4 PID: 96 Comm: kworker/4:1 Not tainted 6.4.0amd_1-next-20230519-dirty #10\n[    6.120665] Hardware name: AMD Birman-PHX/Birman-PHX, BIOS SFH_with_HPD_SEN.FD 04/05/2023\n[    6.120667] Workqueue: events amd_sfh_work_buffer [amd_sfh]\n[    6.120687] Call Trace:\n[    6.120690]  \u003cTASK\u003e\n[    6.120694]  dump_stack_lvl+0x48/0x70\n[    6.120704]  dump_stack+0x10/0x20\n[    6.120707]  ubsan_epilogue+0x9/0x40\n[    6.120716]  __ubsan_handle_shift_out_of_bounds+0x10f/0x170\n[    6.120720]  ? psi_group_change+0x25f/0x4b0\n[    6.120729]  float_to_int.cold+0x18/0xba [amd_sfh]\n[    6.120739]  get_input_rep+0x57/0x340 [amd_sfh]\n[    6.120748]  ? __schedule+0xba7/0x1b60\n[    6.120756]  ? __pfx_get_input_rep+0x10/0x10 [amd_sfh]\n[    6.120764]  amd_sfh_work_buffer+0x91/0x180 [amd_sfh]\n[    6.120772]  process_one_work+0x229/0x430\n[    6.120780]  worker_thread+0x4a/0x3c0\n[    6.120784]  ? __pfx_worker_thread+0x10/0x10\n[    6.120788]  kthread+0xf7/0x130\n[    6.120792]  ? __pfx_kthread+0x10/0x10\n[    6.120795]  ret_from_fork+0x29/0x50\n[    6.120804]  \u003c/TASK\u003e\n...\n\nFix this by adding the condition to validate shift ranges.","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":"HID: amd_sfh: Fix for shift-out-of-bounds","id":"CVE-2023-53703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe()","id":"CVE-2023-53704"},"packages":[],"prev":{"headline":"s390/crypto: use vector instructions only if available for ChaCha20","id":"CVE-2023-53702"},"products":["Linux"],"published":"2025-10-22","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-05-11","vendors":["Linux"]},"summary":"A shift-out-of-bounds error in the AMD SFH HID driver can cause a kernel crash, requiring a patch to validate shift ranges.","url":"https://insights.sbomify.com/CVE-2023-53703/"}