{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-46073 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-46073 is a medium-severity vulnerability in Linux kernel, published on 27 May 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-46073 and fix it if it is affected.\n\nWhat it is: CVE-2026-46073 is a medium-severity vulnerability in Linux kernel, published on 27 May 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-46073 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-2026-46073/ (Markdown: https://insights.sbomify.com/CVE-2026-46073/index.md)","id":"CVE-2026-46073","markdown":"https://insights.sbomify.com/CVE-2026-46073/index.md","name":"CVE-2026-46073","record":{"aliases":["BELL-CVE-2026-46073","DEBIAN-CVE-2026-46073","GHSA-4x22-m2xr-v7q7","ROOT-OS-UBUNTU-2404-CVE-2026-46073","UBUNTU-CVE-2026-46073"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel memory via the PowerZ hardware monitoring driver when a signal interrupts a USB transfer.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nhwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt\n\nwait_for_completion_interruptible_timeout() returns -ERESTARTSYS when\ninterrupted. This needs to abort the URB and return an error. No data\nhas been received from the device so any reads from the transfer\nbuffer are invalid.\n\nThe original code tests !ret, which only catches the timeout case (0).\nOn signal delivery (-ERESTARTSYS), !ret is false so the function skips\nusb_kill_urb() and falls through to read from the unfilled transfer\nbuffer.\n\nFix by capturing the return value into a long (matching the function\nreturn type) and handling signal (negative) and timeout (zero) cases\nwith separate checks that both call usb_kill_urb() before returning.","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":"hwmon: (powerz) Fix missing usb_kill_urb() on signal interrupt","id":"CVE-2026-46073","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"spi: ch341: fix memory leaks on probe failures","id":"CVE-2026-46074"},"packages":[],"prev":{"headline":"ntfs3: add buffer boundary checks to run_unpack()","id":"CVE-2026-46072"},"products":["Linux"],"published":"2026-05-27","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-06-14","vendors":["Linux"]},"summary":"A local attacker can read uninitialized kernel memory via the PowerZ hardware monitoring driver when a signal interrupts a USB transfer.","url":"https://insights.sbomify.com/CVE-2026-46073/"}