{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97948 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97948 is a denial of service vulnerability in Linux, published on 25 Sep 2026. 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-2026-97948 and fix it if it is affected.\n\nWhat it is: CVE-2026-97948 is a denial of service vulnerability in Linux, published on 25 Sep 2026. 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-2026-97948 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-2026-97948/ (Markdown: https://insights.sbomify.com/CVE-2026-97948/index.md)","id":"CVE-2026-97948","markdown":"https://insights.sbomify.com/CVE-2026-97948/index.md","name":"CVE-2026-97948","record":{"aliases":["AZL-104546","BELL-CVE-2026-97948","DEBIAN-CVE-2026-97948","GHSA-wgj5-j7wg-2jm2","UBUNTU-CVE-2026-97948"],"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 recursive locking bug in the Linux kernel's PowerPC EEH subsystem can cause a system hang when specific hardware errors occur.","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\npowerpc/eeh: Fix recursive locking on devices without EEH sensitive driver\n\nThe commit 1010b4c012b0 (\"powerpc/eeh: Make EEH driver device hotplug\nsafe\") refactored the EEH code such that the pci_rescan_remove_lock is\nheld at the beginning of eeh_handle_normal_event() and the\neeh_reset_device() is called with that lock being held. Looks like the\ncommit missed to remove the existing lock/unlock inside eeh_rmv_device()\nwhich is no longer necessary. This is causing the eehd to hang on the\nlock which it actually holds when that code path is taken.\n\n[\u003c0\u003e] 0xc00000011c78f870\n[\u003c0\u003e] __switch_to+0xfc/0x1a0\n[\u003c0\u003e] pci_lock_rescan_remove+0x30/0x44\n[\u003c0\u003e] eeh_rmv_device+0x290/0x2e0\n[\u003c0\u003e] eeh_pe_dev_traverse+0x80/0x130\n[\u003c0\u003e] eeh_reset_device+0xcc/0x23c\n[\u003c0\u003e] eeh_handle_normal_event+0x830/0xa80\n[\u003c0\u003e] eeh_event_handler+0xf8/0x190\n[\u003c0\u003e] kthread+0x194/0x1b0\n[\u003c0\u003e] start_kernel_thread+0x14/0x18\n\nThe issue is seen for cases where the errors are detected on the PHB\ndirectly AND|OR for devices where the driver error_detected() returns\nPCI_ERS_RESULT_NEED_RESET, and driver being not EEH sensitive(i.e no\nerror handlers like slot_reset(), resume() etc defined).","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":"powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver","id":"CVE-2026-97948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"configfs: unhash the dentry before dropping the item in rmdir","id":"CVE-2026-97949"},"packages":[],"prev":{"headline":"x86/amd_node: Fix potential NULL pointer dereference","id":"CVE-2026-97947"},"products":["Linux"],"published":"2026-09-25","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-10-19","vendors":["Linux"]},"summary":"A recursive locking bug in the Linux kernel's PowerPC EEH subsystem can cause a system hang when specific hardware errors occur.","url":"https://insights.sbomify.com/CVE-2026-97948/"}