{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90359 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90359 is a memory corruption vulnerability in Linux, published on 17 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-90359 and fix it if it is affected.\n\nWhat it is: CVE-2026-90359 is a memory corruption vulnerability in Linux, published on 17 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-90359 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-90359/ (Markdown: https://insights.sbomify.com/CVE-2026-90359/index.md)","id":"CVE-2026-90359","markdown":"https://insights.sbomify.com/CVE-2026-90359/index.md","name":"CVE-2026-90359","record":{"aliases":["AZL-102201","BELL-CVE-2026-90359","DEBIAN-CVE-2026-90359","GHSA-h885-6xr2-hvv3","UBUNTU-CVE-2026-90359"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel BPF","requires_auth":"high_privilege","summary":"A local attacker with high privileges can corrupt memory and leak data by attaching BPF programs to functions returning 16-byte values.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nbpf: Reject \u003e8 byte return values on return-reading trampoline paths\n\nbtf_distill_func_proto() builds the function model used for the\nfentry/fexit/fmod_ret/fsession trampolines and struct_ops. It has\naccepted a 16-byte __int128 return value since the trampoline was\nintroduced: __get_type_size() returns the integer's type size, and the\nreturn-type check only rejected ret \u003c 0.\n\nBut the BPF trampoline preserves only 8 bytes of the return value (RAX on\nx86, i.e. R0). For an attach type that reads the target's return value the\nsecond half (RDX / R3) is neither saved nor restored, so a program\nattached to a function returning a 16-byte value corrupts the value seen\nby the real caller and itself observes only half of it. struct_ops\ntrampolines have the same limitation.\n\nThis affects the attach types that read the target's return value: fexit,\nfmod_ret and fsession (plus the _multi variants of fexit and fsession),\nand struct_ops. fentry/fentry_multi run before the target returns and are\nunaffected.\n\nReject a \u003e8 byte return value for these attach types in\nbpf_check_attach_target() and bpf_check_attach_btf_id_multi(), and for\nstruct_ops in bpf_struct_ops_desc_init().","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":"bpf: Reject \u003e8 byte return values on return-reading trampoline paths","id":"CVE-2026-90359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"regulator: core: use system_freezable_wq for init complete work","id":"CVE-2026-90360"},"packages":[],"prev":{"headline":"bpf, x86: Fix trampoline stack size for 128-bit arguments","id":"CVE-2026-90358"},"products":["Linux"],"published":"2026-09-17","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-21","vendors":["Linux"]},"summary":"A local attacker with high privileges can corrupt memory and leak data by attaching BPF programs to functions returning 16-byte values.","url":"https://insights.sbomify.com/CVE-2026-90359/"}