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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-43285— mm/slab: do not access current->mems_allowed_seq if !allow_spin

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存在安全漏洞,该漏洞源于在NMI环境中访问current->mems_allowed_seq,可能导致锁状态不一致。

AI Predicted 5.5 Difficulty: Theoretical EPSS 0.16% · P5

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux af92793e52c3a99b828ed4bdd277fd3e11c18d08< 353dd9934447b9193643ae1afd938607a74d4915 affected
af92793e52c3a99b828ed4bdd277fd3e11c18d08< efd767ddcef0669bbd33c6a823ea0a88f06d4b29 affected
af92793e52c3a99b828ed4bdd277fd3e11c18d08< 144080a5823b2dbd635acb6decf7ab23182664f3 affected
6.18 affected
< 6.18 unaffected
6.18.16≤ 6.18.* unaffected
6.19.6≤ 6.19.* unaffected
7.0≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-43285

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
mm/slab: do not access current->mems_allowed_seq if !allow_spin
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not access current->mems_allowed_seq if !allow_spin Lockdep complains when get_from_any_partial() is called in an NMI context, because current->mems_allowed_seq is seqcount_spinlock_t and not NMI-safe: ================================ WARNING: inconsistent lock state 6.19.0-rc5-kfree-rcu+ #315 Tainted: G N -------------------------------- inconsistent {INITIAL USE} -> {IN-NMI} usage. kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes: ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00 {INITIAL USE} state was registered at: lock_acquire+0x185/0x320 kernel_init_freeable+0x391/0x1150 kernel_init+0x1f/0x220 ret_from_fork+0x736/0x8f0 ret_from_fork_asm+0x1a/0x30 irq event stamp: 56 hardirqs last enabled at (55): [<ffffffff850a68d7>] _raw_spin_unlock_irq+0x27/0x70 hardirqs last disabled at (56): [<ffffffff850858ca>] __schedule+0x2a8a/0x6630 softirqs last enabled at (0): [<ffffffff81536711>] copy_process+0x1dc1/0x6a10 softirqs last disabled at (0): [<0000000000000000>] 0x0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&____s->seqcount#3); <Interrupt> lock(&____s->seqcount#3); *** DEADLOCK *** According to Documentation/locking/seqlock.rst, seqcount_t is not NMI-safe and seqcount_latch_t should be used when read path can interrupt the write-side critical section. In this case, do not access current->mems_allowed_seq and avoid retry.
Source: CVE Program / CVE List V5
CVSS Information
N/A
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存在安全漏洞,该漏洞源于在NMI环境中访问current->mems_allowed_seq,可能导致锁状态不一致。
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 af92793e52c3a99b828ed4bdd277fd3e11c18d08 ~ 353dd9934447b9193643ae1afd938607a74d4915 -
Linux Linux 6.18 -

II. Public POCs for CVE-2026-43285

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

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-43285

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

Patches & Fixes for CVE-2026-43285 (3)

Same Patch Batch · Linux · 2026-05-08 · 197 CVEs total

CVE-2026-43341 9.8 CRITICAL net/ipv6: ioam6: prevent schema length wraparound in trace fill
CVE-2026-43402 9.8 CRITICAL kthread: consolidate kthread exit paths to prevent use-after-free
CVE-2026-43414 9.8 CRITICAL scsi: qla2xxx: Completely fix fcport double free
CVE-2026-43384 9.8 CRITICAL net/tcp-ao: Fix MAC comparison to be constant-time
CVE-2026-43304 9.8 CRITICAL libceph: define and enforce CEPH_MAX_KEY_LEN
CVE-2026-43379 9.8 CRITICAL ksmbd: fix use-after-free in smb_lazy_parent_lease_break_close()
CVE-2026-43376 9.8 CRITICAL ksmbd: fix use-after-free by using call_rcu() for oplock_info
CVE-2026-43465 9.8 CRITICAL net/mlx5e: RX, Fix XDP multi-buf frag counting for striding RQ
CVE-2026-43378 9.8 CRITICAL smb: server: fix use-after-free in smb2_open()
CVE-2026-43383 9.4 CRITICAL net/tcp-md5: Fix MAC comparison to be constant-time
CVE-2026-43406 9.1 CRITICAL libceph: prevent potential out-of-bounds reads in process_message_header()
CVE-2026-43407 9.1 CRITICAL libceph: Fix potential out-of-bounds access in ceph_handle_auth_reply()
CVE-2026-43284 8.8 HIGH xfrm: esp: avoid in-place decrypt on shared skb frags
CVE-2026-43334 8.8 HIGH Bluetooth: SMP: force responder MITM requirements before building the pairing response
CVE-2026-43322 8.8 HIGH Bluetooth: hci_sync: Fix UAF in le_read_features_complete
CVE-2026-43403 8.8 HIGH nsfs: tighten permission checks for ns iteration ioctls
CVE-2026-43391 8.8 HIGH nsfs: tighten permission checks for handle opening
CVE-2026-43291 8.3 HIGH net: nfc: nci: Fix parameter validation for packet data
CVE-2026-43365 8.2 HIGH xfs: fix undersized l_iclog_roundoff values
CVE-2026-43466 8.2 HIGH net/mlx5e: Fix DMA FIFO desync on error CQE SQ recovery

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

IV. Related Vulnerabilities

V. Comments for CVE-2026-43285

No comments yet


Leave a comment