{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53563 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53563 is a medium-severity denial of service vulnerability in Linux kernel, published on 4 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-53563 and fix it if it is affected.\n\nWhat it is: CVE-2023-53563 is a medium-severity denial of service vulnerability in Linux kernel, published on 4 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-53563 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-53563/ (Markdown: https://insights.sbomify.com/CVE-2023-53563/index.md)","id":"CVE-2023-53563","markdown":"https://insights.sbomify.com/CVE-2023-53563/index.md","name":"CVE-2023-53563","record":{"aliases":["BELL-CVE-2023-53563","DEBIAN-CVE-2023-53563","GHSA-jjx2-jhcm-j26c","UBUNTU-CVE-2023-53563"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A missing resource release in the amd-pstate-ut kernel driver causes a system hang or panic when changing CPU frequency modes.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","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\ncpufreq: amd-pstate-ut: Fix kernel panic when loading the driver\n\nAfter loading the amd-pstate-ut driver, amd_pstate_ut_check_perf()\nand amd_pstate_ut_check_freq() use cpufreq_cpu_get() to get the policy\nof the CPU and mark it as busy.\n\nIn these functions, cpufreq_cpu_put() should be used to release the\npolicy, but it is not, so any other entity trying to access the policy\nis blocked indefinitely.\n\nOne such scenario is when amd_pstate mode is changed, leading to the\nfollowing splat:\n\n[ 1332.103727] INFO: task bash:2929 blocked for more than 120 seconds.\n[ 1332.110001]       Not tainted 6.5.0-rc2-amd-pstate-ut #5\n[ 1332.115315] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 1332.123140] task:bash            state:D stack:0     pid:2929  ppid:2873   flags:0x00004006\n[ 1332.123143] Call Trace:\n[ 1332.123145]  \u003cTASK\u003e\n[ 1332.123148]  __schedule+0x3c1/0x16a0\n[ 1332.123154]  ? _raw_read_lock_irqsave+0x2d/0x70\n[ 1332.123157]  schedule+0x6f/0x110\n[ 1332.123160]  schedule_timeout+0x14f/0x160\n[ 1332.123162]  ? preempt_count_add+0x86/0xd0\n[ 1332.123165]  __wait_for_common+0x92/0x190\n[ 1332.123168]  ? __pfx_schedule_timeout+0x10/0x10\n[ 1332.123170]  wait_for_completion+0x28/0x30\n[ 1332.123173]  cpufreq_policy_put_kobj+0x4d/0x90\n[ 1332.123177]  cpufreq_policy_free+0x157/0x1d0\n[ 1332.123178]  ? preempt_count_add+0x58/0xd0\n[ 1332.123180]  cpufreq_remove_dev+0xb6/0x100\n[ 1332.123182]  subsys_interface_unregister+0x114/0x120\n[ 1332.123185]  ? preempt_count_add+0x58/0xd0\n[ 1332.123187]  ? __pfx_amd_pstate_change_driver_mode+0x10/0x10\n[ 1332.123190]  cpufreq_unregister_driver+0x3b/0xd0\n[ 1332.123192]  amd_pstate_change_driver_mode+0x1e/0x50\n[ 1332.123194]  store_status+0xe9/0x180\n[ 1332.123197]  dev_attr_store+0x1b/0x30\n[ 1332.123199]  sysfs_kf_write+0x42/0x50\n[ 1332.123202]  kernfs_fop_write_iter+0x143/0x1d0\n[ 1332.123204]  vfs_write+0x2df/0x400\n[ 1332.123208]  ksys_write+0x6b/0xf0\n[ 1332.123210]  __x64_sys_write+0x1d/0x30\n[ 1332.123213]  do_syscall_64+0x60/0x90\n[ 1332.123216]  ? fpregs_assert_state_consistent+0x2e/0x50\n[ 1332.123219]  ? exit_to_user_mode_prepare+0x49/0x1a0\n[ 1332.123223]  ? irqentry_exit_to_user_mode+0xd/0x20\n[ 1332.123225]  ? irqentry_exit+0x3f/0x50\n[ 1332.123226]  ? exc_page_fault+0x8e/0x190\n[ 1332.123228]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n[ 1332.123232] RIP: 0033:0x7fa74c514a37\n[ 1332.123234] RSP: 002b:00007ffe31dd0788 EFLAGS: 00000246 ORIG_RAX: 0000000000000001\n[ 1332.123238] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007fa74c514a37\n[ 1332.123239] RDX: 0000000000000008 RSI: 000055e27c447aa0 RDI: 0000000000000001\n[ 1332.123241] RBP: 000055e27c447aa0 R08: 00007fa74c5d1460 R09: 000000007fffffff\n[ 1332.123242] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000008\n[ 1332.123244] R13: 00007fa74c61a780 R14: 00007fa74c616600 R15: 00007fa74c615a00\n[ 1332.123247]  \u003c/TASK\u003e\n\nFix this by calling cpufreq_cpu_put() wherever necessary.\n\n[ rjw: Subject and changelog edits ]","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":"cpufreq: amd-pstate-ut: Fix kernel panic when loading the driver","id":"CVE-2023-53563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"ocfs2: fix defrag path triggering jbd2 ASSERT","id":"CVE-2023-53564"},"packages":[],"prev":{"headline":"drm/msm: fix vram leak on bind errors","id":"CVE-2023-53562"},"products":["Linux"],"published":"2025-10-04","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A missing resource release in the amd-pstate-ut kernel driver causes a system hang or panic when changing CPU frequency modes.","url":"https://insights.sbomify.com/CVE-2023-53563/"}