{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98274 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98274 is a vulnerability in Linux, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98274 and fix it if it is affected.\n\nWhat it is: CVE-2026-98274 is a vulnerability in Linux, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98274 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-98274/ (Markdown: https://insights.sbomify.com/CVE-2026-98274/index.md)","id":"CVE-2026-98274","markdown":"https://insights.sbomify.com/CVE-2026-98274/index.md","name":"CVE-2026-98274","record":{"aliases":["BELL-CVE-2026-98274","DEBIAN-CVE-2026-98274","GHSA-566p-8rmw-5xmj","UBUNTU-CVE-2026-98274"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A logic conflict in the Linux kernel PSP implementation with TLS ULP could lead to undefined behavior, requiring specific network configurations to exploit.","user_interaction":"not_required","vuln_class":"other"},"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\nnet: psp: avoid conflicts with skb-\u003edecrypted and sk_validate_xmit_skb()\n\nPSP conflicts with TLS ULP in its usage of both skb-\u003edecrypted and\nsk-\u003esk_validate_xmit_skb().\n\nMake PSP mutually exclusive with TLS ULP, the only other user of either\nof these. As other users of skb-\u003edecrypted come along, they can be added\nto sk_has_decrypt_user(). It would make sense to also assert that\nsk-\u003esk_validate_xmit_skb() is also NULL in both of these setup paths for\nsimilar future proofing, but the PSP listener/sk_clone() path is still\nbroken and it could be seen as a regression to not allow rx assoc to run\non a child of a listener socket with PSP tx assoc state.\n\nInclude all TCP ULPs in the sk_has_decrypt_user() check, even though TLS\nis the only one that conflicts with PSP via the decrypted bit. This is\nintentional because PSP was not designed to be used with ULPs. It is\nbest to close off surface area that may make bugs reachable, until\nsomeone wishes to design and test an actual user of PSP with ULPs.","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":"net: psp: avoid conflicts with skb-\u003edecrypted and sk_validate_xmit_skb()","id":"CVE-2026-98274","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"net: ethernet: cortina: Ack RX overrun interrupt correctly","id":"CVE-2026-98275"},"packages":[],"prev":{"headline":"x86/kprobes: Fix crash when probing CS CALL instructions","id":"CVE-2026-98273"},"products":["Linux"],"published":"2026-10-06","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 logic conflict in the Linux kernel PSP implementation with TLS ULP could lead to undefined behavior, requiring specific network configurations to exploit.","url":"https://insights.sbomify.com/CVE-2026-98274/"}