CVE & CISA-KEV Catalog

CVE-2024-36963

HIGH
7.8
CVSS v3
NVD

Description

In the Linux kernel, the following vulnerability has been resolved: tracefs: Reset permissions on remount if permissions are options There's an inconsistency with the way permissions are handled in tracefs. Because the permissions are generated when accessed, they default to the root inode's permission if they were never set by the user. If the user sets the permissions, then a flag is set and the permissions are saved via the inode (for tracefs files) or an internal attribute field (for eventfs). But if a remount happens that specify the permissions, all the files that were not changed by the user gets updated, but the ones that were are not. If the user were to remount the file system with a given permission, then all files and directories within that file system should be updated. This can cause security issues if a file's permission was updated but the admin forgot about it. They could incorrectly think that remounting with permissions set would update all files, but miss some. For example: # cd /sys/kernel/tracing # chgrp 1002 current_tracer # ls -l [..] -rw-r----- 1 root root 0 May 1 21:25 buffer_size_kb -rw-r----- 1 root root 0 May 1 21:25 buffer_subbuf_size_kb -r--r----- 1 root root 0 May 1 21:25 buffer_total_size_kb -rw-r----- 1 root lkp 0 May 1 21:25 current_tracer -rw-r----- 1 root root 0 May 1 21:25 dynamic_events -r--r----- 1 root root 0 May 1 21:25 dyn_ftrace_total_info -r--r----- 1 root root 0 May 1 21:25 enabled_functions Where current_tracer now has group "lkp". # mount -o remount,gid=1001 . # ls -l -rw-r----- 1 root tracing 0 May 1 21:25 buffer_size_kb -rw-r----- 1 root tracing 0 May 1 21:25 buffer_subbuf_size_kb -r--r----- 1 root tracing 0 May 1 21:25 buffer_total_size_kb -rw-r----- 1 root lkp 0 May 1 21:25 current_tracer -rw-r----- 1 root tracing 0 May 1 21:25 dynamic_events -r--r----- 1 root tracing 0 May 1 21:25 dyn_ftrace_total_info -r--r----- 1 root tracing 0 May 1 21:25 enabled_functions Everything changed but the "current_tracer". Add a new link list that keeps track of all the tracefs_inodes which has the permission flags that tell if the file/dir should use the root inode's permission or not. Then on remount, clear all the flags so that the default behavior of using the root inode's permission is done for all files and directories.

How to fix

Remediation Available
linuxDebian
Fixed in:6.8.11-1CVE-2024-36963
Fixed in:6.8.11-1CVE-2024-36963
linuxUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-awsUbuntu
Fixed in:6.8.0-1013.14USN-6949-1
linux-gcpUbuntu
Fixed in:6.8.0-1012.13USN-6949-1
linux-gkeUbuntu
Fixed in:6.8.0-1008.11USN-6949-1
linux-ibmUbuntu
Fixed in:6.8.0-1010.10USN-6949-1
linux-image-6.8.0-1008-gkeUbuntu
Fixed in:6.8.0-1008.11USN-6949-1
linux-image-6.8.0-1009-raspiUbuntu
Fixed in:6.8.0-1009.10USN-6949-2
linux-image-6.8.0-1010-ibmUbuntu
Fixed in:6.8.0-1010.10USN-6949-1
linux-image-6.8.0-1010-oemUbuntu
Fixed in:6.8.0-1010.10USN-6955-1
linux-image-6.8.0-1010-oracleUbuntu
Fixed in:6.8.0-1010.10USN-6952-1
linux-image-6.8.0-1010-oracle-64kUbuntu
Fixed in:6.8.0-1010.10USN-6952-1
linux-image-6.8.0-1011-nvidiaUbuntu
Fixed in:6.8.0-1011.11~22.04.1USN-6949-1
Fixed in:6.8.0-1011.11USN-6949-1
linux-image-6.8.0-1011-nvidia-64kUbuntu
Fixed in:6.8.0-1011.11~22.04.1USN-6949-1
Fixed in:6.8.0-1011.11USN-6949-1
linux-image-6.8.0-1011-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1011.11.1USN-6952-1
linux-image-6.8.0-1011-nvidia-lowlatency-64kUbuntu
Fixed in:6.8.0-1011.11.1USN-6952-1
linux-image-6.8.0-1012-gcpUbuntu
Fixed in:6.8.0-1012.13USN-6949-1
linux-image-6.8.0-1013-awsUbuntu
Fixed in:6.8.0-1013.14USN-6949-1
linux-image-6.8.0-40-genericUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-6.8.0-40-generic-64kUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-6.8.0-40-lowlatencyUbuntu
Fixed in:6.8.0-40.40.1USN-6949-2
linux-image-6.8.0-40-lowlatency-64kUbuntu
Fixed in:6.8.0-40.40.1USN-6949-2
linux-image-awsUbuntu
Fixed in:6.8.0-1013.14USN-6949-1
linux-image-gcpUbuntu
Fixed in:6.8.0-1012.13USN-6949-1
linux-image-genericUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-generic-64kUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-generic-64k-hwe-24.04Ubuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-generic-hwe-24.04Ubuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-generic-lpaeUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-gkeUbuntu
Fixed in:6.8.0-1008.11USN-6949-1
linux-image-ibmUbuntu
Fixed in:6.8.0-1010.10USN-6949-1
linux-image-ibm-classicUbuntu
Fixed in:6.8.0-1010.10USN-6949-1
linux-image-ibm-lts-24.04Ubuntu
Fixed in:6.8.0-1010.10USN-6949-1
linux-image-kvmUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-lowlatencyUbuntu
Fixed in:6.8.0-40.40.1USN-6949-2
linux-image-lowlatency-64kUbuntu
Fixed in:6.8.0-40.40.1USN-6949-2
linux-image-nvidiaUbuntu
Fixed in:6.8.0-1011.11USN-6949-1
linux-image-nvidia-6.8Ubuntu
Fixed in:6.8.0-1011.11~22.04.1USN-6949-1
linux-image-nvidia-64kUbuntu
Fixed in:6.8.0-1011.11USN-6949-1
linux-image-nvidia-64k-6.8Ubuntu
Fixed in:6.8.0-1011.11~22.04.1USN-6949-1
linux-image-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1011.11.1USN-6952-1
linux-image-nvidia-lowlatency-64kUbuntu
Fixed in:6.8.0-1011.11.1USN-6952-1
linux-image-oem-24.04Ubuntu
Fixed in:6.8.0-1010.10USN-6955-1
linux-image-oem-24.04aUbuntu
Fixed in:6.8.0-1010.10USN-6955-1
linux-image-oracleUbuntu
Fixed in:6.8.0-1010.10USN-6952-1
linux-image-oracle-64kUbuntu
Fixed in:6.8.0-1010.10USN-6952-1
linux-image-raspiUbuntu
Fixed in:6.8.0-1009.10USN-6949-2
linux-image-virtualUbuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-image-virtual-hwe-24.04Ubuntu
Fixed in:6.8.0-40.40USN-6949-1
linux-lowlatencyUbuntu
Fixed in:6.8.0-40.40.1USN-6949-2
linux-nvidiaUbuntu
Fixed in:6.8.0-1011.11USN-6949-1
linux-nvidia-6.8Ubuntu
Fixed in:6.8.0-1011.11~22.04.1USN-6949-1
linux-nvidia-lowlatencyUbuntu
Fixed in:6.8.0-1011.11.1USN-6952-1
linux-oem-6.8Ubuntu
Fixed in:6.8.0-1010.10USN-6955-1
linux-oracleUbuntu
Fixed in:6.8.0-1010.10USN-6952-1
linux-raspiUbuntu
Fixed in:6.8.0-1009.10USN-6949-2

Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploit Intelligence

0.19%probability of exploitation in 30 days
9thpercentile

Low risk: more likely to be exploited than 9% of all known CVEs.

References

Related Vulnerabilities

Other CWE-863 (Incorrect Authorization) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-22518Critical9.8100%KEV + RansomFix
CVE-2023-38035Critical9.8100%KEV + Ransom-
CVE-2022-46169Critical9.8100%KEVFix
CVE-2025-29927Critical9.1100%-Fix
CVE-2024-38856Critical9.899%KEVFix
CVE-2020-36289Medium5.399%-Fix
Embed a live status badge for CVE-2024-36963
CVE-2024-36963 severity badge

Markdown

[![CVE-2024-36963](https://tridentstack.com/cve/badge/CVE-2024-36963.svg)](https://tridentstack.com/cve/CVE-2024-36963)

HTML

<a href="https://tridentstack.com/cve/CVE-2024-36963"><img src="https://tridentstack.com/cve/badge/CVE-2024-36963.svg" alt="CVE-2024-36963"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Start free

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-09-17.