# CVE-2024-36963: linux: In the Linux kernel, the following vulnerability has been resolved:  tracefs: Reset permissions on remount if permiss...

CVE-2024-36963 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-36963, released June 3, 2024. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2024-36963
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0019
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jun 3, 2024

## 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.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.8.11-1 | [DEBIAN-CVE-2024-36963](https://patchblox.com/security/data/fix/linux/debian-cve-2024-36963.md) | Jun 3, 2024 |
| Linux | linux Debian 14 | 6.8.11-1 | [DEBIAN-CVE-2024-36963](https://patchblox.com/security/data/fix/linux/debian-cve-2024-36963.md) | Jun 3, 2024 |

---

Data as of 2026-11-09T13:31:49Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
