🛡️ UBUNTU-CVE-2025-71102
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: scs: fix a wrong parameter in __scs_magic __scs_magic() needs a 'void *' variable, but a 'struct task_struct *' is given. 'task_scs(tsk)' is the starting address of the task's shadow call stack, and '__scs_magic(task_scs(tsk))' is the end address of the task's shadow call stack. Here should be '__scs_magic(task_scs(tsk))'. The user-visible effect of this bug is that when CONFIG_DEBUG_STACK_USAGE is enabled, the shadow call stack usage checking function (scs_check_usage) would scan an incorrect memory range. This could lead 1. **Inaccurate stack usage reporting**: The function would calculate wrong usage statistics for the shadow call stack, potentially showing incorrect value in kmsg. 2. **Potential kernel crash**: If the value of __scs_magic(tsk)is greater than that of __scs_magic(task_scs(tsk)), the for loop may access unmapped memory, potentially causing a kernel panic. However, this scenario is unlikely because task_struct is allocated via the slab allocator (which typically returns lower addresses), while the shadow call stack returned by task_scs(tsk) is allocated via vmalloc(which typically returns higher addresses). However, since this is purely a debugging feature (CONFIG_DEBUG_STACK_USAGE), normal production systems should be not unaffected. The bug only impacts developers and testers who are actively debugging stack usage with this configuration enabled.

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-01-14
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.17.0-22.22
linux-allwinner-5.19
linux-aws 6.17.0-1012.12
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1103.110~20.04.1
linux-aws-5.19
linux-aws-5.3
linux-aws-5.8
linux-aws-6.14
linux-aws-6.17 6.17.0-1012.12~24.04.1
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1052.55~22.04.1
linux-aws-fips 6.8.0-1052.55+fips1
linux-azure 6.17.0-1013.13
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1110.119~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.8
linux-azure-6.11
linux-azure-6.14
linux-azure-6.17 6.17.0-1013.13~24.04.1
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.14
linux-azure-fde-6.17
linux-azure-fde-6.2
linux-azure-fde-6.8
linux-azure-fips 6.8.0-1053.59+fips1
linux-azure-nvidia
linux-azure-nvidia-6.14
linux-bluefield
linux-fips 6.8.0-110.110+fips2
linux-gcp 6.17.0-1012.12
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1103.112~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.8
linux-gcp-6.11
linux-gcp-6.14
linux-gcp-6.17 6.17.0-1012.12~24.04.1
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1054.57~22.04.1
linux-gcp-fips 6.8.0-1054.57+fips1
linux-gke 6.8.0-1050.56
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1037.40
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-173.183~20.04.1
linux-hwe-5.19
linux-hwe-5.8
linux-hwe-6.11
linux-hwe-6.14
linux-hwe-6.17 6.17.0-22.22~24.04.1
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-110.110~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1051.51
linux-ibm-5.15 5.15.0-1097.100~20.04.1
linux-ibm-6.8 6.8.0-1051.51~22.04.1
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1094.96
linux-intel-iotg 5.15.0-1098.104
linux-intel-iotg-5.15 5.15.0-1098.104~20.04.1
linux-kvm 5.15.0-1095.100
linux-lowlatency 6.8.0-110.110.1
linux-lowlatency-hwe-5.15 5.15.0-173.183~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.11
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-110.110.1~22.04.1
linux-nvidia 6.8.0-1051.54
linux-nvidia-6.11
linux-nvidia-6.17 6.17.0-1018.18
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1051.54~22.04.1
linux-nvidia-lowlatency 6.8.0-1051.54.1
linux-nvidia-tegra 6.8.0-1022.22
linux-nvidia-tegra-5.15 5.15.0-1055.55~20.04.1
linux-nvidia-tegra-igx 5.15.0-1044.44
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.11
linux-oem-6.14
linux-oem-6.17 6.17.0-1020.20
linux-oem-6.5
linux-oem-6.8
linux-oracle 6.17.0-1011.11
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1100.106~20.04.1
linux-oracle-5.3
linux-oracle-5.8
linux-oracle-6.14
linux-oracle-6.17 6.17.0-1011.11~24.04.1
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1049.50~22.04.1
linux-raspi 6.17.0-1013.13
linux-raspi-realtime 6.8.0-2042.43
linux-raspi2
linux-realtime 6.17.0-1010.11
linux-realtime-6.14
linux-realtime-6.17 6.17.0-1010.11~24.04.1
linux-realtime-6.8 6.8.1-1047.48~22.04.1
linux-riscv 6.17.0-22.22.1
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1097.101~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.14
linux-riscv-6.17 6.17.0-22.22.1~24.04.1
linux-riscv-6.5
linux-riscv-6.8 6.8.0-110.110~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1028.29
linux-xilinx-zynqmp 5.15.0-1067.71

References

Similar Threats

Patch Gap Protection

Running software with known vulnerabilities?

BotEraser can help reduce exposure by blocking IPs associated with exploit activity — even before a patch is available.

Start Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.