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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2023-53713— arm64: sme: Use STR P to clear FFR context field in streaming SVE mode

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存在安全漏洞，该漏洞源于在流式SVE模式下使用不当存储指令清除FFR上下文字段，可能导致内存损坏。

CVSS 7.8 · High EPSS 0.15% · P4

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 10

VendorProduct Version RangeStatus
Linux Linux 9f5848665788a0f07bc175cb2cdd06d367b7556e< 97669214944e80d3756657c21c4f286f3da6a423 affected
9f5848665788a0f07bc175cb2cdd06d367b7556e< 8769a62faacbbb6cac5e35d9047ce445183d4e9f affected
9f5848665788a0f07bc175cb2cdd06d367b7556e< 1403a899153a12d93fd510e463fd6d0eafba4336 affected
9f5848665788a0f07bc175cb2cdd06d367b7556e< 893b24181b4c4bf1fa2841b1ed192e5413a97cb1 affected
5.16 affected
< 5.16 unaffected
6.1.39≤ 6.1.* unaffected
6.3.13≤ 6.3.* unaffected
… +2 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-53713

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
arm64: sme: Use STR P to clear FFR context field in streaming SVE mode
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: arm64: sme: Use STR P to clear FFR context field in streaming SVE mode The FFR is a predicate register which can vary between 16 and 256 bits in size depending upon the configured vector length. When saving the SVE state in streaming SVE mode, the FFR register is inaccessible and so commit 9f5848665788 ("arm64/sve: Make access to FFR optional") simply clears the FFR field of the in-memory context structure. Unfortunately, it achieves this using an unconditional 8-byte store and so if the SME vector length is anything other than 64 bytes in size we will either fail to clear the entire field or, worse, we will corrupt memory immediately following the structure. This has led to intermittent kfence splats in CI [1] and can trigger kmalloc Redzone corruption messages when running the 'fp-stress' kselftest: | ============================================================================= | BUG kmalloc-1k (Not tainted): kmalloc Redzone overwritten | ----------------------------------------------------------------------------- | | 0xffff000809bf1e22-0xffff000809bf1e27 @offset=7714. First byte 0x0 instead of 0xcc | Allocated in do_sme_acc+0x9c/0x220 age=2613 cpu=1 pid=531 | __kmalloc+0x8c/0xcc | do_sme_acc+0x9c/0x220 | ... Replace the 8-byte store with a store of a predicate register which has been zero-initialised with PFALSE, ensuring that the entire field is cleared in memory. [1] https://lore.kernel.org/r/CA+G9fYtU7HsV0R0dp4XEH5xXHSJFw8KyDf5VQrLLfMxWfxQkag@mail.gmail.com
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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存在安全漏洞，该漏洞源于在流式SVE模式下使用不当存储指令清除FFR上下文字段，可能导致内存损坏。
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 9f5848665788a0f07bc175cb2cdd06d367b7556e ~ 97669214944e80d3756657c21c4f286f3da6a423 -
Linux Linux 5.16 -

II. Public POCs for CVE-2023-53713

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

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53713

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

Same Patch Batch · Linux · 2025-10-22 · 67 CVEs total

CVE-2023-53711 8.2 HIGH NFS: Fix a potential data corruption
CVE-2023-53705 8.2 HIGH ipv6: Fix out-of-bounds access in ipv6_find_tlv()
CVE-2023-53718 7.8 HIGH ring-buffer: Do not swap cpu_buffer during resize process
CVE-2023-53729 7.8 HIGH soc: qcom: qmi_encdec: Restrict string length in decode
CVE-2023-53698 7.8 HIGH xsk: fix refcount underflow in error path
CVE-2022-50581 7.8 HIGH hfs: fix OOB Read in __hfs_brec_find
CVE-2023-53695 7.8 HIGH udf: Detect system inodes linked into directory hierarchy
CVE-2023-53707 7.8 HIGH drm/amdgpu: Fix integer overflow in amdgpu_cs_pass1
CVE-2023-53692 7.8 HIGH ext4: fix use-after-free read in ext4_find_extent for bigalloc + inline
CVE-2022-50567 7.8 HIGH fs: jfs: fix shift-out-of-bounds in dbAllocAG
CVE-2022-50570 7.8 HIGH platform/chrome: fix memory corruption in ioctl
CVE-2022-50569 7.8 HIGH xfrm: Update ipcomp_scratches with NULL when freed
CVE-2023-53726 7.1 HIGH arm64: csum: Fix OoB access in IP checksum code for negative lengths
CVE-2023-53702 s390/crypto: use vector instructions only if available for ChaCha20
CVE-2023-53710 wifi: mt76: mt7921: fix error code of return in mt7921_acpi_read
CVE-2023-53704 clk: imx: clk-imx8mp: improve error handling in imx8mp_clocks_probe()
CVE-2023-53714 drm/stm: ltdc: fix late dereference check
CVE-2023-53706 mm/vmemmap/devdax: fix kernel crash when probing devdax devices
CVE-2023-53712 ARM: 9317/1: kexec: Make smp stop calls asynchronous
CVE-2023-53719 serial: arc_uart: fix of_iomap leak in `arc_serial_probe`

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

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2023-53713

No comments yet

Leave a comment