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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-50194— arm64: probes: Fix uprobes for big-endian kernels

EPSS 0.01% · P3
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-50194

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: probes: Fix uprobes for big-endian kernels
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: arm64: probes: Fix uprobes for big-endian kernels The arm64 uprobes code is broken for big-endian kernels as it doesn't convert the in-memory instruction encoding (which is always little-endian) into the kernel's native endianness before analyzing and simulating instructions. This may result in a few distinct problems: * The kernel may may erroneously reject probing an instruction which can safely be probed. * The kernel may erroneously erroneously permit stepping an instruction out-of-line when that instruction cannot be stepped out-of-line safely. * The kernel may erroneously simulate instruction incorrectly dur to interpretting the byte-swapped encoding. The endianness mismatch isn't caught by the compiler or sparse because: * The arch_uprobe::{insn,ixol} fields are encoded as arrays of u8, so the compiler and sparse have no idea these contain a little-endian 32-bit value. The core uprobes code populates these with a memcpy() which similarly does not handle endianness. * While the uprobe_opcode_t type is an alias for __le32, both arch_uprobe_analyze_insn() and arch_uprobe_skip_sstep() cast from u8[] to the similarly-named probe_opcode_t, which is an alias for u32. Hence there is no endianness conversion warning. Fix this by changing the arch_uprobe::{insn,ixol} fields to __le32 and adding the appropriate __le32_to_cpu() conversions prior to consuming the instruction encoding. The core uprobes copies these fields as opaque ranges of bytes, and so is unaffected by this change. At the same time, remove MAX_UINSN_BYTES and consistently use AARCH64_INSN_SIZE for clarity. Tested with the following: | #include <stdio.h> | #include <stdbool.h> | | #define noinline __attribute__((noinline)) | | static noinline void *adrp_self(void) | { | void *addr; | | asm volatile( | " adrp %x0, adrp_self\n" | " add %x0, %x0, :lo12:adrp_self\n" | : "=r" (addr)); | } | | | int main(int argc, char *argv) | { | void *ptr = adrp_self(); | bool equal = (ptr == adrp_self); | | printf("adrp_self => %p\n" | "adrp_self() => %p\n" | "%s\n", | adrp_self, ptr, equal ? "EQUAL" : "NOT EQUAL"); | | return 0; | } .... where the adrp_self() function was compiled to: | 00000000004007e0 <adrp_self>: | 4007e0: 90000000 adrp x0, 400000 <__ehdr_start> | 4007e4: 911f8000 add x0, x0, #0x7e0 | 4007e8: d65f03c0 ret Before this patch, the ADRP is not recognized, and is assumed to be steppable, resulting in corruption of the result: | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL | # echo 'p /root/adrp-self:0x007e0' > /sys/kernel/tracing/uprobe_events | # echo 1 > /sys/kernel/tracing/events/uprobes/enable | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0xffffffffff7e0 | NOT EQUAL After this patch, the ADRP is correctly recognized and simulated: | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL | # | # echo 'p /root/adrp-self:0x007e0' > /sys/kernel/tracing/uprobe_events | # echo 1 > /sys/kernel/tracing/events/uprobes/enable | # ./adrp-self | adrp_self => 0x4007e0 | adrp_self() => 0x4007e0 | EQUAL
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 9842ceae9fa8deae141533d52a6ead7666962c09 ~ b6a638cb600e13f94b5464724eaa6ab7f3349ca2 -
LinuxLinux 4.10 -

II. Public POCs for CVE-2024-50194

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-50194

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-11-08 · 38 CVEs total

CVE-2024-50203bpf, arm64: Fix address emission with tag-based KASAN enabled
CVE-2024-50193x86/entry_32: Clear CPU buffers after register restore in NMI return
CVE-2024-50195posix-clock: Fix missing timespec64 check in pc_clock_settime()
CVE-2024-50196pinctrl: ocelot: fix system hang on level based interrupts
CVE-2024-50197pinctrl: intel: platform: fix error path in device_for_each_child_node()
CVE-2024-50198iio: light: veml6030: fix IIO device retrieval from embedded device
CVE-2024-50199mm/swapfile: skip HugeTLB pages for unuse_vma
CVE-2024-50200maple_tree: correct tree corruption on spanning store
CVE-2024-50201drm/radeon: Fix encoder->possible_clones
CVE-2024-50202nilfs2: propagate directory read errors from nilfs_find_entry()
CVE-2024-50192irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
CVE-2024-50204fs: don't try and remove empty rbtree node
CVE-2024-50205ALSA: firewire-lib: Avoid division by zero in apply_constraint_to_size()
CVE-2024-50206net: ethernet: mtk_eth_soc: fix memory corruption during fq dma init
CVE-2024-50207ring-buffer: Fix reader locking when changing the sub buffer order
CVE-2024-50209RDMA/bnxt_re: Add a check for memory allocation
CVE-2024-50208RDMA/bnxt_re: Fix a bug while setting up Level-2 PBL pages
CVE-2024-50210posix-clock: posix-clock: Fix unbalanced locking in pc_clock_settime()
CVE-2024-50211udf: refactor inode_bmap() to handle error
CVE-2024-50183scsi: lpfc: Ensure DA_ID handling completion before deleting an NPIV instance

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

IV. Related Vulnerabilities

V. Comments for CVE-2024-50194

No comments yet


Leave a comment