{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43006 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43006 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 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-43006 and fix it if it is affected.\n\nWhat it is: CVE-2026-43006 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 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-43006 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-43006/ (Markdown: https://insights.sbomify.com/CVE-2026-43006/index.md)","id":"CVE-2026-43006","markdown":"https://insights.sbomify.com/CVE-2026-43006/index.md","name":"CVE-2026-43006","record":{"aliases":["BELL-CVE-2026-43006","DEBIAN-CVE-2026-43006","GHSA-5mwr-6pqp-c5qm","UBUNTU-CVE-2026-43006"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger an out-of-bounds read in the Linux kernel's io_uring subsystem, potentially leaking memory or causing a crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/rsrc: reject zero-length fixed buffer import\n\nvalidate_fixed_range() admits buf_addr at the exact end of the\nregistered region when len is zero, because the check uses strict\ngreater-than (buf_end \u003e imu-\u003eubuf + imu-\u003elen).  io_import_fixed()\nthen computes offset == imu-\u003elen, which causes the bvec skip logic\nto advance past the last bio_vec entry and read bv_offset from\nout-of-bounds slab memory.\n\nReturn early from io_import_fixed() when len is zero.  A zero-length\nimport has no data to transfer and should not walk the bvec array\nat all.\n\n  BUG: KASAN: slab-out-of-bounds in io_import_reg_buf+0x697/0x7f0\n  Read of size 4 at addr ffff888002bcc254 by task poc/103\n  Call Trace:\n   io_import_reg_buf+0x697/0x7f0\n   io_write_fixed+0xd9/0x250\n   __io_issue_sqe+0xad/0x710\n   io_issue_sqe+0x7d/0x1100\n   io_submit_sqes+0x86a/0x23c0\n   __do_sys_io_uring_enter+0xa98/0x1590\n  Allocated by task 103:\n  The buggy address is located 12 bytes to the right of\n   allocated 584-byte region [ffff888002bcc000, ffff888002bcc248)","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":"io_uring/rsrc: reject zero-length fixed buffer import","id":"CVE-2026-43006","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"accel/qaic: Handle DBC deactivation if the owner went away","id":"CVE-2026-43007"},"packages":[],"prev":{"headline":"hwmon: (tps53679) Fix array access with zero-length block read","id":"CVE-2026-43005"},"products":["Linux"],"published":"2026-05-01","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A local attacker can trigger an out-of-bounds read in the Linux kernel's io_uring subsystem, potentially leaking memory or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-43006/"}