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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-35873— riscv: Fix vector state restore in rt_sigreturn()

EPSS 0.02% · P4
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-35873

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
riscv: Fix vector state restore in rt_sigreturn()
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: riscv: Fix vector state restore in rt_sigreturn() The RISC-V Vector specification states in "Appendix D: Calling Convention for Vector State" [1] that "Executing a system call causes all caller-saved vector registers (v0-v31, vl, vtype) and vstart to become unspecified.". In the RISC-V kernel this is called "discarding the vstate". Returning from a signal handler via the rt_sigreturn() syscall, vector discard is also performed. However, this is not an issue since the vector state should be restored from the sigcontext, and therefore not care about the vector discard. The "live state" is the actual vector register in the running context, and the "vstate" is the vector state of the task. A dirty live state, means that the vstate and live state are not in synch. When vectorized user_from_copy() was introduced, an bug sneaked in at the restoration code, related to the discard of the live state. An example when this go wrong: 1. A userland application is executing vector code 2. The application receives a signal, and the signal handler is entered. 3. The application returns from the signal handler, using the rt_sigreturn() syscall. 4. The live vector state is discarded upon entering the rt_sigreturn(), and the live state is marked as "dirty", indicating that the live state need to be synchronized with the current vstate. 5. rt_sigreturn() restores the vstate, except the Vector registers, from the sigcontext 6. rt_sigreturn() restores the Vector registers, from the sigcontext, and now the vectorized user_from_copy() is used. The dirty live state from the discard is saved to the vstate, making the vstate corrupt. 7. rt_sigreturn() returns to the application, which crashes due to corrupted vstate. Note that the vectorized user_from_copy() is invoked depending on the value of CONFIG_RISCV_ISA_V_UCOPY_THRESHOLD. Default is 768, which means that vlen has to be larger than 128b for this bug to trigger. The fix is simply to mark the live state as non-dirty/clean prior performing the vstate restore.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
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

VendorProductAffected VersionsCPESubscribe
LinuxLinux c2a658d419246108c9bf065ec347355de5ba8a05 ~ 5b16d904e910183181b9d90efa957c787a8ac91b -
LinuxLinux 6.8 -

II. Public POCs for CVE-2024-35873

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-35873

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-05-19 · 82 CVEs total

CVE-2024-35915nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet
CVE-2024-35926crypto: iaa - Fix async_disable descriptor leak
CVE-2024-35912wifi: iwlwifi: mvm: rfi: fix potential response leaks
CVE-2024-35913wifi: iwlwifi: mvm: pick the version of SESSION_PROTECTION_NOTIF
CVE-2024-35911ice: fix memory corruption bug with suspend and rebuild
CVE-2024-35908tls: get psock ref after taking rxlock to avoid leak
CVE-2024-35907mlxbf_gige: call request_irq() after NAPI initialized
CVE-2024-35905bpf: Protect against int overflow for stack access size
CVE-2024-35904selinux: avoid dereference of garbage after mount failure
CVE-2024-35909net: wwan: t7xx: Split 64bit accesses to fix alignment issues
CVE-2024-35914nfsd: Fix error cleanup path in nfsd_rename()
CVE-2024-35916dma-buf: Fix NULL pointer dereference in sanitycheck()
CVE-2024-35917s390/bpf: Fix bpf_plt pointer arithmetic
CVE-2023-52699sysv: don't call sb_bread() with pointers_lock held
CVE-2024-35919media: mediatek: vcodec: adding lock to protect encoder context list
CVE-2024-35920media: mediatek: vcodec: adding lock to protect decoder context list
CVE-2024-35921media: mediatek: vcodec: Fix oops when HEVC init fails
CVE-2024-35922fbmon: prevent division by zero in fb_videomode_from_videomode()
CVE-2024-35924usb: typec: ucsi: Limit read size on v1.2
CVE-2024-35925block: prevent division by zero in blk_rq_stat_sum()

Showing top 20 of 82 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-35873

No comments yet


Leave a comment