CVE-2023-53989— arm64: mm: fix VA-range sanity check
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2023-53989
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: mm: fix VA-range sanity check
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: arm64: mm: fix VA-range sanity check Both create_mapping_noalloc() and update_mapping_prot() sanity-check their 'virt' parameter, but the check itself doesn't make much sense. The condition used today appears to be a historical accident. The sanity-check condition: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } ... can only be true for the KASAN shadow region or the module region, and there's no reason to exclude these specifically for creating and updateing mappings. When arm64 support was first upstreamed in commit: c1cc1552616d0f35 ("arm64: MMU initialisation") ... the condition was: if (virt < VMALLOC_START) { [ ... warning here ... ] return; } At the time, VMALLOC_START was the lowest kernel address, and this was checking whether 'virt' would be translated via TTBR1. Subsequently in commit: 14c127c957c1c607 ("arm64: mm: Flip kernel VA space") ... the condition was changed to: if ((virt >= VA_START) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } This appear to have been a thinko. The commit moved the linear map to the bottom of the kernel address space, with VMALLOC_START being at the halfway point. The old condition would warn for changes to the linear map below this, and at the time VA_START was the end of the linear map. Subsequently we cleaned up the naming of VA_START in commit: 77ad4ce69321abbe ("arm64: memory: rename VA_START to PAGE_END") ... keeping the erroneous condition as: if ((virt >= PAGE_END) && (virt < VMALLOC_START)) { [ ... warning here ... ] return; } Correct the condition to check against the start of the TTBR1 address space, which is currently PAGE_OFFSET. This simplifies the logic, and more clearly matches the "outside kernel range" message in the warning.
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存在安全漏洞，该漏洞源于VA范围检查存在逻辑错误，可能导致映射创建或更新失败。
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
II. Public POCs for CVE-2023-53989
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2023-53989
请登录查看更多情报信息。
Same Patch Batch · Linux · 2025-12-24 · 322 CVEs total
| CVE-2022-50755 | udf: Avoid double brelse() in udf_rename() | |
| CVE-2022-50765 | RISC-V: kexec: Fix memory leak of elf header buffer | |
| CVE-2022-50764 | ipv6/sit: use DEV_STATS_INC() to avoid data-races | |
| CVE-2022-50763 | crypto: marvell/octeontx - prevent integer overflows | |
| CVE-2022-50762 | fs/ntfs3: Avoid UBSAN error on true_sectors_per_clst() | |
| CVE-2022-50760 | drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios() | |
| CVE-2022-50761 | x86/xen: Fix memory leak in xen_init_lock_cpu() | |
| CVE-2022-50759 | media: i2c: ov5648: Free V4L2 fwnode data on unbind | |
| CVE-2022-50758 | staging: vt6655: fix potential memory leak | |
| CVE-2022-50756 | nvme-pci: fix mempool alloc size | |
| CVE-2022-50757 | media: camss: Clean up received buffers on failed start of streaming | |
| CVE-2022-50749 | acct: fix potential integer overflow in encode_comp_t() | |
| CVE-2022-50746 | erofs: validate the extent length for uncompressed pclusters | |
| CVE-2022-50747 | hfs: Fix OOB Write in hfs_asc2mac | |
| CVE-2022-50748 | ipc: mqueue: fix possible memory leak in init_mqueue_fs() | |
| CVE-2022-50750 | drm/panel/panel-sitronix-st7701: Remove panel on DSI attach failure | |
| CVE-2022-50752 | md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() | |
| CVE-2022-50753 | f2fs: fix to do sanity check on summary info | |
| CVE-2022-50754 | apparmor: fix a memleak in multi_transaction_new() | |
| CVE-2022-50766 | btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer |
Showing top 20 of 322 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2023-53989
No comments yet