Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2024-26868— nfs: fix panic when nfs4_ff_layout_prepare_ds() fails

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于空指针取消引用。

CVSS 7.5 · High EPSS 0.61% · P48

Possible ATT&CK Techniques 1 AI

T1059 · Command and Scripting Interpreter

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux b739a5bd9d9f18cc69dced8db128ef7206e000cd< 31db25e3141b20e2a76a9f219eeca52e3cab126c affected
b739a5bd9d9f18cc69dced8db128ef7206e000cd< 7ca651b4ec4a049f5a46a0e5ff921b86b91c47c5 affected
b739a5bd9d9f18cc69dced8db128ef7206e000cd< 5ada9016b1217498fad876a3d5b07645cc955608 affected
b739a5bd9d9f18cc69dced8db128ef7206e000cd< dac068f164ad05b35e7c0be13f138c3f6adca58f affected
b739a5bd9d9f18cc69dced8db128ef7206e000cd< 719fcafe07c12646691bd62d7f8d94d657fa0766 affected
6.1 affected
< 6.1 unaffected
6.1.83≤ 6.1.* unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-26868

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
nfs: fix panic when nfs4_ff_layout_prepare_ds() fails
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: nfs: fix panic when nfs4_ff_layout_prepare_ds() fails We've been seeing the following panic in production BUG: kernel NULL pointer dereference, address: 0000000000000065 PGD 2f485f067 P4D 2f485f067 PUD 2cc5d8067 PMD 0 RIP: 0010:ff_layout_cancel_io+0x3a/0x90 [nfs_layout_flexfiles] Call Trace: <TASK> ? __die+0x78/0xc0 ? page_fault_oops+0x286/0x380 ? __rpc_execute+0x2c3/0x470 [sunrpc] ? rpc_new_task+0x42/0x1c0 [sunrpc] ? exc_page_fault+0x5d/0x110 ? asm_exc_page_fault+0x22/0x30 ? ff_layout_free_layoutreturn+0x110/0x110 [nfs_layout_flexfiles] ? ff_layout_cancel_io+0x3a/0x90 [nfs_layout_flexfiles] ? ff_layout_cancel_io+0x6f/0x90 [nfs_layout_flexfiles] pnfs_mark_matching_lsegs_return+0x1b0/0x360 [nfsv4] pnfs_error_mark_layout_for_return+0x9e/0x110 [nfsv4] ? ff_layout_send_layouterror+0x50/0x160 [nfs_layout_flexfiles] nfs4_ff_layout_prepare_ds+0x11f/0x290 [nfs_layout_flexfiles] ff_layout_pg_init_write+0xf0/0x1f0 [nfs_layout_flexfiles] __nfs_pageio_add_request+0x154/0x6c0 [nfs] nfs_pageio_add_request+0x26b/0x380 [nfs] nfs_do_writepage+0x111/0x1e0 [nfs] nfs_writepages_callback+0xf/0x30 [nfs] write_cache_pages+0x17f/0x380 ? nfs_pageio_init_write+0x50/0x50 [nfs] ? nfs_writepages+0x6d/0x210 [nfs] ? nfs_writepages+0x6d/0x210 [nfs] nfs_writepages+0x125/0x210 [nfs] do_writepages+0x67/0x220 ? generic_perform_write+0x14b/0x210 filemap_fdatawrite_wbc+0x5b/0x80 file_write_and_wait_range+0x6d/0xc0 nfs_file_fsync+0x81/0x170 [nfs] ? nfs_file_mmap+0x60/0x60 [nfs] __x64_sys_fsync+0x53/0x90 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Inspecting the core with drgn I was able to pull this >>> prog.crashed_thread().stack_trace()[0] #0 at 0xffffffffa079657a (ff_layout_cancel_io+0x3a/0x84) in ff_layout_cancel_io at fs/nfs/flexfilelayout/flexfilelayout.c:2021:27 >>> prog.crashed_thread().stack_trace()[0]['idx'] (u32)1 >>> prog.crashed_thread().stack_trace()[0]['flseg'].mirror_array[1].mirror_ds (struct nfs4_ff_layout_ds *)0xffffffffffffffed This is clear from the stack trace, we call nfs4_ff_layout_prepare_ds() which could error out initializing the mirror_ds, and then we go to clean it all up and our check is only for if (!mirror->mirror_ds). This is inconsistent with the rest of the users of mirror_ds, which have if (IS_ERR_OR_NULL(mirror_ds)) to keep from tripping over this exact scenario. Fix this up in ff_layout_cancel_io() to make sure we don't panic when we get an error. I also spot checked all the other instances of checking mirror_ds and we appear to be doing the correct checks everywhere, only unconditionally dereferencing mirror_ds when we know it would be valid.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于空指针取消引用。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux b739a5bd9d9f18cc69dced8db128ef7206e000cd ~ 31db25e3141b20e2a76a9f219eeca52e3cab126c -
Linux Linux 6.1 -

II. Public POCs for CVE-2024-26868

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-26868

请登录查看更多情报信息。

Other References for CVE-2024-26868 (5)

Same Patch Batch · Linux · 2024-04-17 · 100 CVEs total

CVE-2024-26877 9.8 CRITICAL crypto: xilinx - call finalize with bh disabled
CVE-2024-26853 9.8 CRITICAL igc: avoid returning frame twice in XDP_REDIRECT
CVE-2024-26828 9.4 CRITICAL cifs: fix underflow in parse_server_interfaces()
CVE-2024-26856 8.8 HIGH net: sparx5: Fix use after free inside sparx5_del_mact_entry
CVE-2024-26822 8.7 HIGH smb: client: set correct id, uid and cruid for multiuser automounts
CVE-2024-26830 8.4 HIGH i40e: Do not allow untrusted VF to remove administratively set MAC
CVE-2024-26824 7.8 HIGH crypto: algif_hash - Remove bogus SGL free on zero-length error path
CVE-2024-26898 7.8 HIGH aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts
CVE-2024-26852 7.8 HIGH net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
CVE-2024-26895 7.8 HIGH wifi: wilc1000: prevent use-after-free on vif when cleaning up all interfaces
CVE-2024-26890 7.8 HIGH Bluetooth: btrtl: fix out of bounds memory access
CVE-2024-26864 7.8 HIGH tcp: Fix refcnt handling in __inet_hash_connect().
CVE-2024-26865 7.8 HIGH rds: tcp: Fix use-after-free of net in reqsk_timer_handler().
CVE-2024-26869 7.8 HIGH f2fs: fix to truncate meta inode pages forcely
CVE-2024-26870 7.8 HIGH NFSv4.2: fix nfs4_listxattr kernel BUG at mm/usercopy.c:102
CVE-2024-26872 7.8 HIGH RDMA/srpt: Do not register event handler until srpt device is fully setup
CVE-2024-26885 7.8 HIGH bpf: Fix DEVMAP_HASH overflow check on 32-bit arches
CVE-2024-26884 7.8 HIGH bpf: Fix hashtab overflow check on 32-bit arches
CVE-2024-26883 7.8 HIGH bpf: Fix stackmap overflow check on 32-bit arches
CVE-2024-26880 7.8 HIGH dm: call the resume method on internal suspend

Showing top 20 of 100 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2024-26868

No comments yet


Leave a comment