{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40265 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40265 is a vulnerability in Linux, published on 4 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-40265 and fix it if it is affected.\n\nWhat it is: CVE-2025-40265 is a vulnerability in Linux, published on 4 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-40265 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-40265/ (Markdown: https://insights.sbomify.com/CVE-2025-40265/index.md)","id":"CVE-2025-40265","markdown":"https://insights.sbomify.com/CVE-2025-40265/index.md","name":"CVE-2025-40265","record":{"aliases":["BELL-CVE-2025-40265","DEBIAN-CVE-2025-40265","GHSA-h657-cgwg-79mx","UBUNTU-CVE-2025-40265"],"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 missing return value check in the Linux kernel vfat filesystem code allows a local attacker to trigger a kernel panic via a crafted block device, causing denial of service.","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\nvfat: fix missing sb_min_blocksize() return value checks\n\nWhen emulating an nvme device on qemu with both logical_block_size and\nphysical_block_size set to 8 KiB, but without format, a kernel panic\nwas triggered during the early boot stage while attempting to mount a\nvfat filesystem.\n\n[95553.682035] EXT4-fs (nvme0n1): unable to set blocksize\n[95553.684326] EXT4-fs (nvme0n1): unable to set blocksize\n[95553.686501] EXT4-fs (nvme0n1): unable to set blocksize\n[95553.696448] ISOFS: unsupported/invalid hardware sector size 8192\n[95553.697117] ------------[ cut here ]------------\n[95553.697567] kernel BUG at fs/buffer.c:1582!\n[95553.697984] Oops: invalid opcode: 0000 [#1] SMP NOPTI\n[95553.698602] CPU: 0 UID: 0 PID: 7212 Comm: mount Kdump: loaded Not tainted 6.18.0-rc2+ #38 PREEMPT(voluntary)\n[95553.699511] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[95553.700534] RIP: 0010:folio_alloc_buffers+0x1bb/0x1c0\n[95553.701018] Code: 48 8b 15 e8 93 18 02 65 48 89 35 e0 93 18 02 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff c3 cc cc cc cc \u003c0f\u003e 0b 90 66 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f\n[95553.702648] RSP: 0018:ffffd1b0c676f990 EFLAGS: 00010246\n[95553.703132] RAX: ffff8cfc4176d820 RBX: 0000000000508c48 RCX: 0000000000000001\n[95553.703805] RDX: 0000000000002000 RSI: 0000000000000000 RDI: 0000000000000000\n[95553.704481] RBP: ffffd1b0c676f9c8 R08: 0000000000000000 R09: 0000000000000000\n[95553.705148] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001\n[95553.705816] R13: 0000000000002000 R14: fffff8bc8257e800 R15: 0000000000000000\n[95553.706483] FS:  000072ee77315840(0000) GS:ffff8cfdd2c8d000(0000) knlGS:0000000000000000\n[95553.707248] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[95553.707782] CR2: 00007d8f2a9e5a20 CR3: 0000000039d0c006 CR4: 0000000000772ef0\n[95553.708439] PKRU: 55555554\n[95553.708734] Call Trace:\n[95553.709015]  \u003cTASK\u003e\n[95553.709266]  __getblk_slow+0xd2/0x230\n[95553.709641]  ? find_get_block_common+0x8b/0x530\n[95553.710084]  bdev_getblk+0x77/0xa0\n[95553.710449]  __bread_gfp+0x22/0x140\n[95553.710810]  fat_fill_super+0x23a/0xfc0\n[95553.711216]  ? __pfx_setup+0x10/0x10\n[95553.711580]  ? __pfx_vfat_fill_super+0x10/0x10\n[95553.712014]  vfat_fill_super+0x15/0x30\n[95553.712401]  get_tree_bdev_flags+0x141/0x1e0\n[95553.712817]  get_tree_bdev+0x10/0x20\n[95553.713177]  vfat_get_tree+0x15/0x20\n[95553.713550]  vfs_get_tree+0x2a/0x100\n[95553.713910]  vfs_cmd_create+0x62/0xf0\n[95553.714273]  __do_sys_fsconfig+0x4e7/0x660\n[95553.714669]  __x64_sys_fsconfig+0x20/0x40\n[95553.715062]  x64_sys_call+0x21ee/0x26a0\n[95553.715453]  do_syscall_64+0x80/0x670\n[95553.715816]  ? __fs_parse+0x65/0x1e0\n[95553.716172]  ? fat_parse_param+0x103/0x4b0\n[95553.716587]  ? vfs_parse_fs_param_source+0x21/0xa0\n[95553.717034]  ? __do_sys_fsconfig+0x3d9/0x660\n[95553.717548]  ? __x64_sys_fsconfig+0x20/0x40\n[95553.717957]  ? x64_sys_call+0x21ee/0x26a0\n[95553.718360]  ? do_syscall_64+0xb8/0x670\n[95553.718734]  ? __x64_sys_fsconfig+0x20/0x40\n[95553.719141]  ? x64_sys_call+0x21ee/0x26a0\n[95553.719545]  ? do_syscall_64+0xb8/0x670\n[95553.719922]  ? x64_sys_call+0x1405/0x26a0\n[95553.720317]  ? do_syscall_64+0xb8/0x670\n[95553.720702]  ? __x64_sys_close+0x3e/0x90\n[95553.721080]  ? x64_sys_call+0x1b5e/0x26a0\n[95553.721478]  ? do_syscall_64+0xb8/0x670\n[95553.721841]  ? irqentry_exit+0x43/0x50\n[95553.722211]  ? exc_page_fault+0x90/0x1b0\n[95553.722681]  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[95553.723166] RIP: 0033:0x72ee774f3afe\n[95553.723562] Code: 73 01 c3 48 8b 0d 0a 33 0f 00 f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 49 89 ca b8 af 01 00 00 0f 05 \u003c48\u003e 3d 01 f0 ff ff 73 01 c3 48 8b 0d da 32 0f 00 f7 d8 64 89 01 48\n[95553.725188] RSP: 002b:00007ffe97148978 EFLAGS: 00000246 ORIG_RAX: 00000000000001af\n[95553.725892] RAX: ffffffffffffffda RBX: \n---truncated---","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":"vfat: fix missing sb_min_blocksize() return value checks","id":"CVE-2025-40265","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"KVM: arm64: Check the untrusted offset in FF-A memory share","id":"CVE-2025-40266"},"packages":[],"prev":{"headline":"be2net: pass wrb_params in case of OS2BMC","id":"CVE-2025-40264"},"products":["Linux"],"published":"2025-12-04","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-05-11","vendors":["Linux"]},"summary":"A missing return value check in the Linux kernel vfat filesystem code allows a local attacker to trigger a kernel panic via a crafted block device, causing denial of service.","url":"https://insights.sbomify.com/CVE-2025-40265/"}