[LTS 9.2] arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array #219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[LTS 9.2]
CVE-2025-21785
VULN-54130
Problem
https://www.cve.org/CVERecord?id=CVE-2025-21785
Solution
The official fix in the mainline kernel is provided in the 875d742 commit
The 5.15 backport (closest to
ciqlts9_2
kernel version 5.14) is provided in the 88a3e6afaf002250220793df99404977d343db14 commit, and it has no differences compared to the mainline solution.kABI check: passed
Boot test: passed
boot-test.log
Kselftests: passed relative
Methodology
The tests were run using the rocky-patching framework (qemu-kvm virtualization of Rocky base cloud aarch64 images) ported to the local WHLE-LS1046A machine, based on the NXP Layerscape LS1046A arm64 processor.
kernel-selftests-internal
package:bpf
tests, exceptbpf:test_kmod.sh
,bpf:test_progs
,bpf:test_progs-no_alu32
(unstable, can crash the machine).exec
,kexec
,lkdtm
,net/forwarding
,netfilter
.Coverage
arm64/bti
,arm64/fp
,arm64/mte
,arm64/pauth
,arm64/signal
,arm64/tags
,bpf
,breakpoints
,capabilities
,cgroup
,clone3
,core
,cpu-hotplug
,cpufreq
,drivers/dma-buf
,drivers/net/bonding
,drivers/net/team
,efivarfs
,filesystems
,filesystems/binderfs
,filesystems/epoll
,firmware
,fpu
,ftrace
,futex
,gpio
,intel_pstate
,ipc
,ir
,kcmp
,kvm
,landlock
,lib
,livepatch
,membarrier
,memfd
,memory-hotplug
,mincore
,mount
,mqueue
,nci
,net
,net/mptcp
,nsfs
,openat2
,pid_namespace
,pidfd
,proc
,pstore
,ptrace
,rlimits
,rseq
,rtc
,seccomp
,sgx
,sigaltstack
,size
,splice
,static_keys
,sync
,syscall_user_dispatch
,sysctl
,tc-testing
,tdx
,timens
,timers
,tmpfs
,tpm2
,user
,vDSO
,vm
,zram
Reference
kselftests–mix–ciqlts9_2–run1.log
kselftests–mix–ciqlts9_2–run2.log
kselftests–mix–ciqlts9_2–run3.log
kselftests–mix–ciqlts9_2–run4.log
kselftests–mix–ciqlts9_2–run5.log
Patch
kselftests–mix–ciqlts9_2-CVE-2025-21785–run1.log
kselftests–mix–ciqlts9_2-CVE-2025-21785–run2.log
Comparison
The different results are all contained in the reference run:
Differences highlights
cgroup:test_freezer
Inconsistent results for the
test_cgfreezer_ptrace
.net:gro.sh
Inconsistent results for the ip6 packet geometry.
proc:proc-uptime-001
Unspecified internal problem with the testing binary.
timers:raw_skew
Well-known issue with the external clock adjustments.
Specific tests: skipped
To be done on demand