{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-64359 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64359 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jul 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-64359 and fix it if it is affected.\n\nWhat it is: CVE-2026-64359 is a medium-severity denial of service vulnerability in Linux kernel, published on 25 Jul 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-64359 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-64359/ (Markdown: https://insights.sbomify.com/CVE-2026-64359/index.md)","id":"CVE-2026-64359","markdown":"https://insights.sbomify.com/CVE-2026-64359/index.md","name":"CVE-2026-64359","record":{"aliases":["BELL-CVE-2026-64359","DEBIAN-CVE-2026-64359","GHSA-7cjq-w44j-qx9w","ROOT-OS-UBUNTU-2204-CVE-2026-64359","UBUNTU-CVE-2026-64359"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel nilfs2","requires_auth":"low_privilege","summary":"A local attacker can cause a denial of service in the Linux kernel by triggering a hung task in the nilfs2 filesystem via invalid segment numbers in an ioctl call.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers\n\nSyzbot reported a hung task in nilfs_transaction_begin() where multiple\ntasks performing chmod() on a nilfs2 mount blocked for over 143 seconds\nwaiting to acquire ns_segctor_sem for read:\n\n  INFO: task syz.0.17:5918 blocked for more than 143 seconds.\n  Call Trace:\n   schedule+0x164/0x360\n   rwsem_down_read_slowpath+0x6d9/0x940\n   down_read+0x99/0x2e0\n   nilfs_transaction_begin+0x364/0x710 fs/nilfs2/segment.c:221\n   nilfs_setattr+0x124/0x2c0 fs/nilfs2/inode.c:921\n   notify_change+0xc1a/0xf40\n   chmod_common+0x273/0x4a0\n   do_fchmodat+0x12d/0x230\n\nThe writer holding ns_segctor_sem was a concurrent\nNILFS_IOCTL_CLEAN_SEGMENTS caller, stuck inside printk while emitting\nper-element warnings from nilfs_sufile_updatev():\n\n   __nilfs_msg+0x373/0x450 fs/nilfs2/super.c:78\n   nilfs_sufile_updatev+0x21c/0x6d0 fs/nilfs2/sufile.c:186\n   nilfs_sufile_freev fs/nilfs2/sufile.h:93 [inline]\n   nilfs_free_segments fs/nilfs2/segment.c:1140 [inline]\n   nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1261 [inline]\n   nilfs_segctor_do_construct+0x1f55/0x76c0\n   nilfs_clean_segments+0x3bd/0xa50\n   nilfs_ioctl_clean_segments fs/nilfs2/ioctl.c:922 [inline]\n   nilfs_ioctl+0x261f/0x2780\n\nThe root cause is that user-supplied segment numbers are not validated\nbefore nilfs_clean_segments() begins doing work; the range check on\neach segnum is performed deep inside the call chain by\nnilfs_sufile_updatev(), which emits a nilfs_warn() per invalid entry\nwhile still holding the segctor lock and the sufile mi_sem.  Under load\n(repeated invocations across multiple mounts saturating the global\nprintk path), the cumulative printk latency keeps ns_segctor_sem held\nlong enough to trip the hung_task watchdog, blocking concurrent\noperations such as chmod() that need ns_segctor_sem for read.\n\nFix by validating the contents of kbufs[4] in nilfs_clean_segments()\nimmediately after acquiring ns_segctor_sem via nilfs_transaction_lock().\nHolding ns_segctor_sem serializes the check against\nnilfs_ioctl_resize(), which can modify ns_nsegments, so the validation\nuses a consistent value.  Out-of-range segment numbers are rejected\nwith -EINVAL before any segment-cleaning work begins, so the bad\nentries never reach the per-element diagnostic path inside\nnilfs_sufile_updatev().","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":"nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers","id":"CVE-2026-64359","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"hfs/hfsplus: zero-initialize buffer in hfs_bnode_read","id":"CVE-2026-64360"},"packages":[],"prev":{"headline":"media: mtk-jpeg: cancel workqueue on release for supported platforms only","id":"CVE-2026-64358"},"products":["Linux"],"published":"2026-07-25","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker can cause a denial of service in the Linux kernel by triggering a hung task in the nilfs2 filesystem via invalid segment numbers in an ioctl call.","url":"https://insights.sbomify.com/CVE-2026-64359/"}