{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97927 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97927 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-97927 and fix it if it is affected.\n\nWhat it is: CVE-2026-97927 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-97927 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-97927/ (Markdown: https://insights.sbomify.com/CVE-2026-97927/index.md)","id":"CVE-2026-97927","markdown":"https://insights.sbomify.com/CVE-2026-97927/index.md","name":"CVE-2026-97927","record":{"aliases":["AZL-104765","BELL-CVE-2026-97927","DEBIAN-CVE-2026-97927","GHSA-vf26-9r8x-769m","UBUNTU-CVE-2026-97927"],"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":"none","summary":"A local attacker can cause a kernel crash by mounting a crafted UFS filesystem image that fails during cylinder group loading.","user_interaction":"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\nufs: create the root dentry after loading cylinder metadata\n\nufs_fill_super() installed sb-\u003es_root before it loaded the cylinder\ngroup structures for a writable mount:\n\n\tsb-\u003es_root = d_make_root(inode);\n\t...\n\tif (!sb_rdonly(sb))\n\t\tif (!ufs_read_cylinder_structures(sb))\n\t\t\tgoto failed;\n\nWhen ufs_read_cylinder_structures() failed, the error path freed the\nin-core superblock information and set sb-\u003es_fs_info to NULL while\nsb-\u003es_root stayed installed. get_tree_bdev() then reached\ndeactivate_locked_super(), and because s_root was present,\ngeneric_shutdown_super() called sync_filesystem() and the put_super\noperation. Both dereference UFS_SB(sb), which is now NULL, so a mount\nthat fails only while reading the cylinder groups oopses during\nteardown. A crafted image whose first cylinder group cannot be read\nreaches this path.\n\nLoad the cylinder group metadata first and create the root dentry last,\nso the superblock is published to the VFS only once it is fully set up.\nufs_setup_cstotal() and ufs_read_cylinder_structures() take only the\nsuper_block and do not use the root inode, so the reordering is safe.","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":"ufs: create the root dentry after loading cylinder metadata","id":"CVE-2026-97927","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"drm/amdgpu: skip the VMID 0 flush for VRAM","id":"CVE-2026-97928"},"packages":[],"prev":{"headline":"ufs: validate cylinder group metadata before caching it","id":"CVE-2026-97926"},"products":["Linux"],"published":"2026-09-25","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 local attacker can cause a kernel crash by mounting a crafted UFS filesystem image that fails during cylinder group loading.","url":"https://insights.sbomify.com/CVE-2026-97927/"}