{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68229 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68229 is a vulnerability in Linux, published on 16 Dec 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-68229 and fix it if it is affected.\n\nWhat it is: CVE-2025-68229 is a vulnerability in Linux, published on 16 Dec 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-68229 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-68229/ (Markdown: https://insights.sbomify.com/CVE-2025-68229/index.md)","id":"CVE-2025-68229","markdown":"https://insights.sbomify.com/CVE-2025-68229/index.md","name":"CVE-2025-68229","record":{"aliases":["AZL-72466","BELL-CVE-2025-68229","DEBIAN-CVE-2025-68229","GHSA-984g-3ggq-r83h","ROOT-OS-DEBIAN-12-CVE-2025-68229","ROOT-OS-DEBIAN-13-CVE-2025-68229","ROOT-OS-UBUNTU-2204-CVE-2025-68229","ROOT-OS-UBUNTU-2404-CVE-2025-68229","UBUNTU-CVE-2025-68229"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel SCSI target","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel crash via a null pointer dereference in the tcm_loop SCSI target module when reading configfs attributes.","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\nscsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()\n\nIf the allocation of tl_hba-\u003esh fails in tcm_loop_driver_probe() and we\nattempt to dereference it in tcm_loop_tpg_address_show() we will get a\nsegfault, see below for an example. So, check tl_hba-\u003esh before\ndereferencing it.\n\n  Unable to allocate struct scsi_host\n  BUG: kernel NULL pointer dereference, address: 0000000000000194\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 0 P4D 0\n  Oops: 0000 [#1] PREEMPT SMP NOPTI\n  CPU: 1 PID: 8356 Comm: tokio-runtime-w Not tainted 6.6.104.2-4.azl3 #1\n  Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 09/28/2024\n  RIP: 0010:tcm_loop_tpg_address_show+0x2e/0x50 [tcm_loop]\n...\n  Call Trace:\n   \u003cTASK\u003e\n   configfs_read_iter+0x12d/0x1d0 [configfs]\n   vfs_read+0x1b5/0x300\n   ksys_read+0x6f/0xf0\n...","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":"scsi: target: tcm_loop: Fix segfault in tcm_loop_tpg_address_show()","id":"CVE-2025-68229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"drm/amdgpu: fix gpu page fault after hibernation on PF passthrough","id":"CVE-2025-68230"},"packages":[],"prev":{"headline":"drm/plane: Fix create_in_format_blob() return value","id":"CVE-2025-68228"},"products":["Linux"],"published":"2025-12-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-16","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash via a null pointer dereference in the tcm_loop SCSI target module when reading configfs attributes.","url":"https://insights.sbomify.com/CVE-2025-68229/"}