CVE-2024-46682
published 2024-09-13CVE-2024-46682: In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open Prior to commit 3f29cc82a84c…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
8.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
Prior to commit 3f29cc82a84c ("nfsd: split sc_status out of
sc_type") states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.
Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.
To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc/fs/nfsd/clients/2/states
[ 513.590804] Call trace:
[ 513.590925] _raw_spin_lock+0xcc/0x160
[ 513.591119] nfs4_show_open+0x78/0x2c0 [nfsd]
[ 513.591412] states_show+0x44c/0x488 [nfsd]
[ 513.591681] seq_read_iter+0x5d8/0x760
[ 513.591896] seq_read+0x188/0x208
[ 513.592075] vfs_read+0x148/0x470
[ 513.592241] ksys_read+0xcc/0x178
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.10.9-1 (forky) | linux 6.10.9-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 3f29cc82a84c23cfd12b903029dd26002ca825f5 < ba0b697de298285301c71c258598226e06494236 | ba0b697de298285301c71c258598226e06494236 |
| linux | linux | >= 3f29cc82a84c23cfd12b903029dd26002ca825f5 < a204501e1743d695ca2930ed25a2be9f8ced96d3 | a204501e1743d695ca2930ed25a2be9f8ced96d3 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.10.9-1 | 6.10.9-1 |
| linux | linux_kernel | >= 0 < 6.10.9-1 | 6.10.9-1 |
| linux | linux_kernel | >= 6.9 < 6.10.8 | 6.10.8 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5LOW
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
vendor_redhat·2024-09-13·CVSS 5.5
CVE-2024-46682 [MEDIUM] CWE-476 kernel: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
kernel: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
In the Linux kernel, the following vulnerability has been resolved:
nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
Prior to commit 3f29cc82a84c ("nfsd: split sc_status out of
sc_type") states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.
Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.
To reproduce: mount the ser
Debian
CVE-2024-46682: linux - In the Linux kernel, the following vulnerability has been resolved: nfsd: preve...
vendor_debian·2024·CVSS 5.5
CVE-2024-46682 [MEDIUM] CVE-2024-46682: linux - In the Linux kernel, the following vulnerability has been resolved: nfsd: preve...
In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open Prior to commit 3f29cc82a84c ("nfsd: split sc_status out of sc_type") states_show() relied on sc_type field to be of valid type before calling into a subfunction to show content of a particular stateid. From that commit, we split the validity of the stateid into sc_status and no longer changed sc_type to 0 while unhashing the stateid. This resulted in kernel oopsing for nfsv4.0 opens that stay around and in nfs4_show_open() would derefence sc_file which was NULL. Instead, for closed open stateids forgo displaying information that relies of having a valid sc_file. To reproduce: mount the server with 4.0, read and close a file and then on the server cat /proc/fs/
OSV
CVE-2024-46682: In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4
osv·2024-09-13·CVSS 5.5
CVE-2024-46682 [MEDIUM] CVE-2024-46682: In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4
In the Linux kernel, the following vulnerability has been resolved: nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open Prior to commit 3f29cc82a84c ("nfsd: split sc_status out of sc_type") states_show() relied on sc_type field to be of valid type before calling into a subfunction to show content of a particular stateid. From that commit, we split the validity of the stateid into sc_status and no longer changed sc_type to 0 while unhashing the stateid. This resulted in kernel oopsing for nfsv4.0 opens that stay around and in nfs4_show_open() would derefence sc_file which was NULL. Instead, for closed open stateids forgo displaying information that relies of having a valid sc_file. To reproduce: mount the server with 4.0, read and close a file and then on the server cat /proc/fs/
GHSA
GHSA-xrjv-8x73-5h7v: In the Linux kernel, the following vulnerability has been resolved:
nfsd: prevent panic for nfsv4
ghsa_unreviewed·2024-09-13
CVE-2024-46682 [MEDIUM] CWE-476 GHSA-xrjv-8x73-5h7v: In the Linux kernel, the following vulnerability has been resolved:
nfsd: prevent panic for nfsv4
In the Linux kernel, the following vulnerability has been resolved:
nfsd: prevent panic for nfsv4.0 closed files in nfs4_show_open
Prior to commit 3f29cc82a84c ("nfsd: split sc_status out of
sc_type") states_show() relied on sc_type field to be of valid
type before calling into a subfunction to show content of a
particular stateid. From that commit, we split the validity of
the stateid into sc_status and no longer changed sc_type to 0
while unhashing the stateid. This resulted in kernel oopsing
for nfsv4.0 opens that stay around and in nfs4_show_open()
would derefence sc_file which was NULL.
Instead, for closed open stateids forgo displaying information
that relies of having a valid sc_file.
To reproduce: mount the server with 4.0, read and close
a file and then on the server cat /proc
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-09-13
Published