Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

redhat логотип

CVE-2026-23053

Опубликовано: 04 фев. 2026
Источник: redhat
CVSS3: 5.3
EPSS Низкий

Описание

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a deadlock involving nfs_release_folio() Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed. It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.

A flaw was found in the Linux kernel. An NFSv4.1 client can experience a deadlock during memory reclaim. This occurs when state recovery waits on kthreadd while kthreadd attempts to reclaim memory by calling nfs_release_folio(), leading to a circular dependency. A local user can trigger this condition by initiating page cache activity on an NFS mount, resulting in hung tasks, system-wide stalls, and a Denial of Service (DoS).

Отчет

An NFSv4.1 client can deadlock during memory reclaim because state recovery may wait on kthreadd while kthreadd attempts to reclaim memory by calling nfs_release_folio. The release path may require recovery to make progress, so the two paths can block each other and lead to hung tasks and system wide stalls. For the CVSS the PR is N because normal users can trigger page cache activity on an NFS mount and memory pressure can occur without special privileges. The issue is not directly network reachable. A remote or unstable server can influence recovery timing but the deadlock manifests on the client under local reclaim conditions. Impact is denial of service due to hung reclaim and stalled NFS operations.

Затронутые пакеты

ПлатформаПакетСостояниеРекомендацияРелиз
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Показывать по

Дополнительная информация

Статус:

Moderate
Дефект:
CWE-400
https://bugzilla.redhat.com/show_bug.cgi?id=2436778kernel: Linux kernel: Denial of Service in NFSv4.1 client due to deadlock during memory reclaim

EPSS

Процентиль: 7%
0.00025
Низкий

5.3 Medium

CVSS3

Связанные уязвимости

ubuntu
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a deadlock involving nfs_release_folio() Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed. It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.

nvd
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a deadlock involving nfs_release_folio() Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed. It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.

debian
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: N ...

github
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a deadlock involving nfs_release_folio() Wang Zhaolong reports a deadlock involving NFSv4.1 state recovery waiting on kthreadd, which is attempting to reclaim memory by calling nfs_release_folio(). The latter cannot make progress due to state recovery being needed. It seems that the only safe thing to do here is to kick off a writeback of the folio, without waiting for completion, or else kicking off an asynchronous commit.

oracle-oval
17 дней назад

ELSA-2026-50144: Unbreakable Enterprise kernel security update (IMPORTANT)

EPSS

Процентиль: 7%
0.00025
Низкий

5.3 Medium

CVSS3