<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 09:28:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53167 — tracing: Fix null pointer dereference in tracing_err_log_open()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53167</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix null pointer dereference in tracing_err_log_open()&lt;/p&gt;
&lt;p&gt;Fix an issue in function &amp;#39;tracing_err_log_open&amp;#39;.
The function doesn&amp;#39;t call &amp;#39;seq_open&amp;#39; if the file is opened only with
write permissions, which results in &amp;#39;file-&amp;gt;private_data&amp;#39; being left as null.
If we then use &amp;#39;lseek&amp;#39; on that opened file, &amp;#39;seq_lseek&amp;#39; dereferences
&amp;#39;file-&amp;gt;private_data&amp;#39; in &amp;#39;mutex_lock(&amp;amp;m-&amp;gt;lock)&amp;#39;, resulting in a kernel panic.
Writing to this node requires root privileges, therefore this bug
has very little security impact.&lt;/p&gt;
&lt;p&gt;Tracefs node: /sys/kernel/tracing/error_log&lt;/p&gt;
&lt;p&gt;Example Kernel panic:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038
Call trace:
 mutex_lock+0x30/0x110
 seq_lseek+0x34/0xb8
 __arm64_sys_lseek+0x6c/0xb8
 invoke_syscall+0x58/0x13c
 el0_svc_common+0xc4/0x10c
 do_el0_svc+0x24/0x98
 el0_svc+0x24/0x88
 el0t_64_sync_handler+0x84/0xe4
 el0t_64_sync+0x1b4/0x1b8
Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02)
---[ end trace 561d1b49c12cf8a5 ]---
Kernel panic - not syncing: Oops: Fatal exception&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Fix null pointer dereference in tracing_err_log_open()&lt;/p&gt;
&lt;p&gt;Fix an issue in function &amp;#39;tracing_err_log_open&amp;#39;.
The function doesn&amp;#39;t call &amp;#39;seq_open&amp;#39; if the file is opened only with
write permissions, which results in &amp;#39;file-&amp;gt;private_data&amp;#39; being left as null.
If we then use &amp;#39;lseek&amp;#39; on that opened file, &amp;#39;seq_lseek&amp;#39; dereferences
&amp;#39;file-&amp;gt;private_data&amp;#39; in &amp;#39;mutex_lock(&amp;amp;m-&amp;gt;lock)&amp;#39;, resulting in a kernel panic.
Writing to this node requires root privileges, therefore this bug
has very little security impact.&lt;/p&gt;
&lt;p&gt;Tracefs node: /sys/kernel/tracing/error_log&lt;/p&gt;
&lt;p&gt;Example Kernel panic:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038
Call trace:
 mutex_lock+0x30/0x110
 seq_lseek+0x34/0xb8
 __arm64_sys_lseek+0x6c/0xb8
 invoke_syscall+0x58/0x13c
 el0_svc_common+0xc4/0x10c
 do_el0_svc+0x24/0x98
 el0_svc+0x24/0x88
 el0t_64_sync_handler+0x84/0xe4
 el0t_64_sync+0x1b4/0x1b8
Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02)
---[ end trace 561d1b49c12cf8a5 ]---
Kernel panic - not syncing: Oops: Fatal exception&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53167</guid>
    </item>
  </channel>
</rss>
