<?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>Thu, 01 Oct 2026 20:27:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72297 — net: atm: reject out-of-range traffic classes in QoS validation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72297</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;net: atm: reject out-of-range traffic classes in QoS validation&lt;/p&gt;
&lt;p&gt;Reject ATM traffic classes above ATM_ANYCLASS in check_tp().
SO_ATMQOS stores the supplied QoS after check_qos() succeeds, so
accepting larger values leaves invalid traffic_class values in
vcc-&amp;gt;qos.&lt;/p&gt;
&lt;p&gt;That bad state later reaches pvc_info(), which indexes class_name[]
with vcc-&amp;gt;qos.{rx,tp}.traffic_class. Values above ATM_ANYCLASS cause
an out-of-bounds read when /proc/net/atm/pvc is read.&lt;/p&gt;
&lt;p&gt;Tighten the existing QoS validation so invalid traffic_class values
are rejected at the point where user supplied QoS is accepted.&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;net: atm: reject out-of-range traffic classes in QoS validation&lt;/p&gt;
&lt;p&gt;Reject ATM traffic classes above ATM_ANYCLASS in check_tp().
SO_ATMQOS stores the supplied QoS after check_qos() succeeds, so
accepting larger values leaves invalid traffic_class values in
vcc-&amp;gt;qos.&lt;/p&gt;
&lt;p&gt;That bad state later reaches pvc_info(), which indexes class_name[]
with vcc-&amp;gt;qos.{rx,tp}.traffic_class. Values above ATM_ANYCLASS cause
an out-of-bounds read when /proc/net/atm/pvc is read.&lt;/p&gt;
&lt;p&gt;Tighten the existing QoS validation so invalid traffic_class values
are rejected at the point where user supplied QoS is accepted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72297</guid>
    </item>
  </channel>
</rss>
