{"id":"OESA-2026-3985","summary":"kernel security update","details":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nconfigfs: fix lockless traversals of ->s_children\n\nHaving the parent directory locked protects entries from removal\nby another thread, but it does *not* protect cursors from being\nmoved around by lseek() - or freed, for that matter.(CVE-2026-74330)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nconfigfs_lookup(): don't leave ->s_dentry dangling on failure\n\nNormally ->s_dentry is cleared when dentry it's pointing to becomes\nnegative (on eviction, realistically).  However, that only happens\nif dentry gets to be positive in the first place; in case of inode\nallocation failure dentry never becomes positive, so ->d_iput()\nis not called at all.\n\nWe do part of what normally would've been done by configfs_d_iput()\n(dropping the reference to configfs_dirent) manually, but we do\nnot clear ->s_dentry there.  Sloppy as it is, it does not matter in\ncase of configfs_create_{dir,link}() - there configfs_dirent does\nnot survive dropping the sole reference to it.\n\nHowever, for configfs_lookup() it *does* survive, with a dangling\npointer to soon to be freed dentry sitting it its ->s_dentry.\n\nSubsequent getdents(2) in that directory will end up dereferencing\nthat pointer in order to pick the inode number.  Use after free...\n\nThis is the minimal fix; the right approach is to set the linkage\nbetween dentry and configfs_dirent only after we know that we have\nan inode, but that takes more surgery and the bug had been there\nsince 2006, so...(CVE-2026-74359)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Pin the 'struct nfs_server' during a FREE_STATEID call\n\nDan Aloni reports that he was able to hit a use-after-free bug if a\nFREE_STATEID operation gets delayed for whatever reason. Fix this by\nbumping the refcount of the 'struct nfs_server' object for the duration\nof the FREE_STATEID so it doesn't get cleaned up from underneath us\nwhile operations are still in flight.(CVE-2026-74730)","modified":"2026-09-20T13:30:32.107662443Z","published":"2026-09-20T13:23:51Z","upstream":["CVE-2026-74330","CVE-2026-74359","CVE-2026-74730"],"database_specific":{"severity":"Critical"},"references":[{"type":"ADVISORY","url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3985"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74330"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74359"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74730"}],"affected":[{"package":{"name":"kernel","ecosystem":"openEuler:20.03-LTS-SP4","purl":"pkg:rpm/openEuler/kernel&distro=openEuler-20.03-LTS-SP4"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.19.90-2609.2.0.0390.oe2003sp4"}]}],"ecosystem_specific":{"x86_64":["bpftool-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","bpftool-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-debugsource-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-devel-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-source-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-tools-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-tools-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","kernel-tools-devel-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","perf-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","python2-perf-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","python2-perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","python3-perf-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm","python3-perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.x86_64.rpm"],"aarch64":["bpftool-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","bpftool-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-debugsource-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-devel-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-source-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-tools-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-tools-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","kernel-tools-devel-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","perf-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","python2-perf-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","python2-perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","python3-perf-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm","python3-perf-debuginfo-4.19.90-2609.2.0.0390.oe2003sp4.aarch64.rpm"],"src":["kernel-4.19.90-2609.2.0.0390.oe2003sp4.src.rpm"]},"database_specific":{"source":"https://repo.openeuler.org/security/data/osv/OESA-2026-3985.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"}]}