{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72458 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72458 is a vulnerability in Linux, published on 15 Aug 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-72458 and fix it if it is affected.\n\nWhat it is: CVE-2026-72458 is a vulnerability in Linux, published on 15 Aug 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-72458 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-72458/ (Markdown: https://insights.sbomify.com/CVE-2026-72458/index.md)","id":"CVE-2026-72458","markdown":"https://insights.sbomify.com/CVE-2026-72458/index.md","name":"CVE-2026-72458","record":{"aliases":["BELL-CVE-2026-72458","DEBIAN-CVE-2026-72458","GHSA-2qpq-46v2-w4c7","UBUNTU-CVE-2026-72458"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A NULL pointer dereference in the AppArmor kernel module allows local attackers to cause a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\napparmor: fix NULL pointer dereference in unpack_pdb\n\npdb-\u003edfa could be NULL if unpack_dfa fails, causing a NULL pointer\ndereference.","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":"apparmor: fix NULL pointer dereference in unpack_pdb","id":"CVE-2026-72458","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"apparmor: aa_label_alloc use aa_label_free on alloc failure","id":"CVE-2026-72459"},"packages":[],"prev":{"headline":"apparmor: fail policy unpack on accept2 allocation failure","id":"CVE-2026-72457"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A NULL pointer dereference in the AppArmor kernel module allows local attackers to cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-72458/"}