<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 13:14:10 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72315</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72315</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72315</guid>
    </item>
    <item>
      <title>EUVD-2026-376134</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-376134</link>
      <description>EUVD-2026-376134</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-376134</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72315</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72315</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix busy dentry warning on unmount after DIO&lt;/p&gt;
&lt;p&gt;Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed
the issue in cifs where deferred close of a file led to a dentry reference
count not being released in umount, by flushing deferredclose_wq in
cifs_kill_sb() to solve it.&lt;/p&gt;
&lt;p&gt;However, the cifs DIO path suffers from the same busy-dentry problem caused
by a delayed dentry reference-count release:&lt;/p&gt;
&lt;p&gt;[dio]			[cifsd]			[close + umount]
netfs_unbuffered_write_iter_locked
...
				cifs_demultiplex_thread
 netfs_unbuffered_write
  cifs_issue_write
  netfs_wait_for_in_progress_stream [1]
				...
				 netfs_write_subrequest_terminated
				  netfs_subreq_clear_in_progress
				   netfs_wake_collector // wake [1]
				  netfs_put_subrequest
 netfs_put_request
  queue_work(system_dfl_wq, xxx) [2]
 // dio write return					cifs_close
							 _cifsFileInfo_put
							  // cfile-&amp;gt;count 2-&amp;gt;1
							  --cfile-&amp;gt;count [3]&lt;/p&gt;
&lt;p&gt;// umount
							cifs_kill_sb
							 kill_anon_super
							  // warning triggered!
							  shrink_dcache_for_umount [4]
[system_dfl_wq] [5]
netfs_free_request
 ...
 _cifsFileInfo_put
  // cfile-&amp;gt;count 1-&amp;gt;0
  --cfile-&amp;gt;count
  queue_work(fileinfo_put_wq, xxx)&lt;/p&gt;
&lt;p&gt;[fileinfo_put_wq] [6]
cifsFileInfo_put_work
 cifsFileInfo_put_final
  dput&lt;/p&gt;
&lt;p&gt;If the umount path is triggered before [5], it results warning:
BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1)
[unmou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix busy dentry warning on unmount after DIO&lt;/p&gt;
&lt;p&gt;Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed
the issue in cifs where deferred close of a file led to a dentry reference
count not being released in umount, by flushing deferredclose_wq in
cifs_kill_sb() to solve it.&lt;/p&gt;
&lt;p&gt;However, the cifs DIO path suffers from the same busy-dentry problem caused
by a delayed dentry reference-count release:&lt;/p&gt;
&lt;p&gt;[dio]			[cifsd]			[close + umount]
netfs_unbuffered_write_iter_locked
...
				cifs_demultiplex_thread
 netfs_unbuffered_write
  cifs_issue_write
  netfs_wait_for_in_progress_stream [1]
				...
				 netfs_write_subrequest_terminated
				  netfs_subreq_clear_in_progress
				   netfs_wake_collector // wake [1]
				  netfs_put_subrequest
 netfs_put_request
  queue_work(system_dfl_wq, xxx) [2]
 // dio write return					cifs_close
							 _cifsFileInfo_put
							  // cfile-&amp;gt;count 2-&amp;gt;1
							  --cfile-&amp;gt;count [3]&lt;/p&gt;
&lt;p&gt;// umount
							cifs_kill_sb
							 kill_anon_super
							  // warning triggered!
							  shrink_dcache_for_umount [4]
[system_dfl_wq] [5]
netfs_free_request
 ...
 _cifsFileInfo_put
  // cfile-&amp;gt;count 1-&amp;gt;0
  --cfile-&amp;gt;count
  queue_work(fileinfo_put_wq, xxx)&lt;/p&gt;
&lt;p&gt;[fileinfo_put_wq] [6]
cifsFileInfo_put_work
 cifsFileInfo_put_final
  dput&lt;/p&gt;
&lt;p&gt;If the umount path is triggered before [5], it results warning:
BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1)
[unmou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72315</guid>
    </item>
    <item>
      <title>GHSA-3544-2m6j-7m5r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3544-2m6j-7m5r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix busy dentry warning on unmount after DIO&lt;/p&gt;
&lt;p&gt;Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed
the issue in cifs where deferred close of a file led to a dentry reference
count not being released in umount, by flushing deferredclose_wq in
cifs_kill_sb() to solve it.&lt;/p&gt;
&lt;p&gt;However, the cifs DIO path suffers from the same busy-dentry problem caused
by a delayed dentry reference-count release:&lt;/p&gt;
&lt;p&gt;[dio]			[cifsd]			[close + umount]
netfs_unbuffered_write_iter_locked
...
				cifs_demultiplex_thread
 netfs_unbuffered_write
  cifs_issue_write
  netfs_wait_for_in_progress_stream [1]
				...
				 netfs_write_subrequest_terminated
				  netfs_subreq_clear_in_progress
				   netfs_wake_collector // wake [1]
				  netfs_put_subrequest
 netfs_put_request
  queue_work(system_dfl_wq, xxx) [2]
 // dio write return					cifs_close
							 _cifsFileInfo_put
							  // cfile-&amp;gt;count 2-&amp;gt;1
							  --cfile-&amp;gt;count [3]&lt;/p&gt;
&lt;p&gt;// umount
							cifs_kill_sb
							 kill_anon_super
							  // warning triggered!
							  shrink_dcache_for_umount [4]
[system_dfl_wq] [5]
netfs_free_request
 ...
 _cifsFileInfo_put
  // cfile-&amp;gt;count 1-&amp;gt;0
  --cfile-&amp;gt;count
  queue_work(fileinfo_put_wq, xxx)&lt;/p&gt;
&lt;p&gt;[fileinfo_put_wq] [6]
cifsFileInfo_put_work
 cifsFileInfo_put_final
  dput&lt;/p&gt;
&lt;p&gt;If the umount path is triggered before [5], it results warning:
BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1)
[unmou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix busy dentry warning on unmount after DIO&lt;/p&gt;
&lt;p&gt;Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed
the issue in cifs where deferred close of a file led to a dentry reference
count not being released in umount, by flushing deferredclose_wq in
cifs_kill_sb() to solve it.&lt;/p&gt;
&lt;p&gt;However, the cifs DIO path suffers from the same busy-dentry problem caused
by a delayed dentry reference-count release:&lt;/p&gt;
&lt;p&gt;[dio]			[cifsd]			[close + umount]
netfs_unbuffered_write_iter_locked
...
				cifs_demultiplex_thread
 netfs_unbuffered_write
  cifs_issue_write
  netfs_wait_for_in_progress_stream [1]
				...
				 netfs_write_subrequest_terminated
				  netfs_subreq_clear_in_progress
				   netfs_wake_collector // wake [1]
				  netfs_put_subrequest
 netfs_put_request
  queue_work(system_dfl_wq, xxx) [2]
 // dio write return					cifs_close
							 _cifsFileInfo_put
							  // cfile-&amp;gt;count 2-&amp;gt;1
							  --cfile-&amp;gt;count [3]&lt;/p&gt;
&lt;p&gt;// umount
							cifs_kill_sb
							 kill_anon_super
							  // warning triggered!
							  shrink_dcache_for_umount [4]
[system_dfl_wq] [5]
netfs_free_request
 ...
 _cifsFileInfo_put
  // cfile-&amp;gt;count 1-&amp;gt;0
  --cfile-&amp;gt;count
  queue_work(fileinfo_put_wq, xxx)&lt;/p&gt;
&lt;p&gt;[fileinfo_put_wq] [6]
cifsFileInfo_put_work
 cifsFileInfo_put_final
  dput&lt;/p&gt;
&lt;p&gt;If the umount path is triggered before [5], it results warning:
BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1)
[unmou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3544-2m6j-7m5r</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-72315 — smb: client: fix busy dentry warning on unmount after DIO</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-72315</link>
      <description>msrc_CVE-2026-72315</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-72315</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72315</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72315</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix busy dentry warning on unmount after DIO Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed the issue in cifs where deferred close of a file led to a dentry reference count not being released in umount, by flushing deferredclose_wq in cifs_kill_sb() to solve it. However, the cifs DIO path suffers from the same busy-dentry problem caused by a delayed dentry reference-count release: 	[dio]			[cifsd]			[close + umount] netfs_unbuffered_write_iter_locked ... 				cifs_demultiplex_thread  netfs_unbuffered_write   cifs_issue_write   netfs_wait_for_in_progress_stream [1] 				... 				 netfs_write_subrequest_terminated 				  netfs_subreq_clear_in_progress 				   netfs_wake_collector // wake [1] 				  netfs_put_subrequest  netfs_put_request   queue_work(system_dfl_wq, xxx) [2]  // dio write return					cifs_close 							 _cifsFileInfo_put 							  // cfile-&amp;gt;count 2-&amp;gt;1 							  --cfile-&amp;gt;count [3] 							// umount 							cifs_kill_sb 							 kill_anon_super 							  // warning triggered! 							  shrink_dcache_for_umount [4] [system_dfl_wq] [5] netfs_free_request  ...  _cifsFileInfo_put   // cfile-&amp;gt;count 1-&amp;gt;0   --cfile-&amp;gt;count   queue_work(fileinfo_put_wq, xxx) [fileinfo_put_wq] [6] cifsFileInfo_put_work  cifsFileInfo_put_final   dput If the umount path is triggered before [5], it results warning: BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1) [unmount of c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 149 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix busy dentry warning on unmount after DIO Commit c68337442f03 (&amp;#34;cifs: Fix busy dentry used after unmounting&amp;#34;) fixed the issue in cifs where deferred close of a file led to a dentry reference count not being released in umount, by flushing deferredclose_wq in cifs_kill_sb() to solve it. However, the cifs DIO path suffers from the same busy-dentry problem caused by a delayed dentry reference-count release: 	[dio]			[cifsd]			[close + umount] netfs_unbuffered_write_iter_locked ... 				cifs_demultiplex_thread  netfs_unbuffered_write   cifs_issue_write   netfs_wait_for_in_progress_stream [1] 				... 				 netfs_write_subrequest_terminated 				  netfs_subreq_clear_in_progress 				   netfs_wake_collector // wake [1] 				  netfs_put_subrequest  netfs_put_request   queue_work(system_dfl_wq, xxx) [2]  // dio write return					cifs_close 							 _cifsFileInfo_put 							  // cfile-&amp;gt;count 2-&amp;gt;1 							  --cfile-&amp;gt;count [3] 							// umount 							cifs_kill_sb 							 kill_anon_super 							  // warning triggered! 							  shrink_dcache_for_umount [4] [system_dfl_wq] [5] netfs_free_request  ...  _cifsFileInfo_put   // cfile-&amp;gt;count 1-&amp;gt;0   --cfile-&amp;gt;count   queue_work(fileinfo_put_wq, xxx) [fileinfo_put_wq] [6] cifsFileInfo_put_work  cifsFileInfo_put_final   dput If the umount path is triggered before [5], it results warning: BUG: Dentry 00000000eab1f070{i=9a917b66ae404fec,n=test}  still in use (1) [unmount of c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72315</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
