{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40022 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40022 is a vulnerability in Linux, published on 24 Oct 2025. 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-2025-40022 and fix it if it is affected.\n\nWhat it is: CVE-2025-40022 is a vulnerability in Linux, published on 24 Oct 2025. 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-2025-40022 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-2025-40022/ (Markdown: https://insights.sbomify.com/CVE-2025-40022/index.md)","id":"CVE-2025-40022","markdown":"https://insights.sbomify.com/CVE-2025-40022/index.md","name":"CVE-2025-40022","record":{"aliases":["BELL-CVE-2025-40022","DEBIAN-CVE-2025-40022","GHSA-rjhr-rr92-fh8c","ROOT-OS-DEBIAN-11-CVE-2025-40022","ROOT-OS-DEBIAN-12-CVE-2025-40022","ROOT-OS-DEBIAN-13-CVE-2025-40022","UBUNTU-CVE-2025-40022"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Incorrect boolean handling in Linux kernel crypto module may cause logic errors, requiring local access 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\ncrypto: af_alg - Fix incorrect boolean values in af_alg_ctx\n\nCommit 1b34cbbf4f01 (\"crypto: af_alg - Disallow concurrent writes in\naf_alg_sendmsg\") changed some fields from bool to 1-bit bitfields of\ntype u32.\n\nHowever, some assignments to these fields, specifically 'more' and\n'merge', assign values greater than 1.  These relied on C's implicit\nconversion to bool, such that zero becomes false and nonzero becomes\ntrue.\n\nWith a 1-bit bitfields of type u32 instead, mod 2 of the value is taken\ninstead, resulting in 0 being assigned in some cases when 1 was intended.\n\nFix this by restoring the bool type.","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":"crypto: af_alg - Fix incorrect boolean values in af_alg_ctx","id":"CVE-2025-40022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"drm/xe/vf: Don't expose sysfs attributes not applicable for VFs","id":"CVE-2025-40023"},"packages":[],"prev":{"headline":"tracing: dynevent: Add a missing lockdown check on dynevent","id":"CVE-2025-40021"},"products":["Linux"],"published":"2025-10-24","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-15","vendors":["Linux"]},"summary":"Incorrect boolean handling in Linux kernel crypto module may cause logic errors, requiring local access to exploit.","url":"https://insights.sbomify.com/CVE-2025-40022/"}