linux-kernel - [PATCH 0/2] nfs: handle failure during allocing lock/unlock data

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250419085355.1451457-1-lilingfeng3@huawei.com>
Date: Sat, 19 Apr 2025 16:53:53 +0800
From: Li Lingfeng <lilingfeng3@...wei.com>
To: <trondmy@...nel.org>, <anna@...nel.org>, <jlayton@...nel.org>,
	<bcodding@...hat.com>
CC: <linux-nfs@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<yukuai1@...weicloud.com>, <houtao1@...wei.com>, <yi.zhang@...wei.com>,
	<yangerkun@...wei.com>, <lilingfeng@...weicloud.com>,
	<lilingfeng3@...wei.com>
Subject: [PATCH 0/2] nfs: handle failure during allocing lock/unlock data

Lack of memory can cause nfs_lock_context allocation failures in unlock
paths, triggering NULL pointer dereference upon unlock completion.
Additionally, failed nfs_open_context acquisition may lead to similar
vulnerabilities. Proper error handling during lock/unlock data
initialization prevents critical faults.

Li Lingfeng (2):
  nfs: handle failure of nfs_get_lock_context in unlock path
  nfs: handle failure of get_nfs_open_context

 fs/nfs/nfs4proc.c | 21 ++++++++++++++++++---
 1 file changed, 18 insertions(+), 3 deletions(-)

-- 
2.31.1