<?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>Tue, 17 Nov 2026 10:10:22 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98919</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98919</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98919</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1469 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</link>
      <description>certfr-2026-avi-1469</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</guid>
    </item>
    <item>
      <title>EUVD-2026-391517</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391517</link>
      <description>EUVD-2026-391517</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391517</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98919</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98919</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: harden adjust_idledly() against divide-by-zero and overflow&lt;/p&gt;
&lt;p&gt;adjust_idledly() has several corner-case issues flagged during review:&lt;/p&gt;
&lt;p&gt;1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.
     The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a
     divide-by-zero and panics the kernel.&lt;/p&gt;
&lt;p&gt;2. The tick-to-ns conversions are done in u32:
        idledly * idledly_units_ps, (maxcnt - 1) * 1000
     Both overflow u32 before DIV_ROUND_CLOSEST() sees them.&lt;/p&gt;
&lt;p&gt;3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.&lt;/p&gt;
&lt;p&gt;4. The register only stores whole ticks, so the clamped ns value has
     to be converted to ticks and back. DIV_ROUND_CLOSEST() can round
     that conversion up past maxcnt:&lt;/p&gt;
&lt;p&gt;maxcnt = 640 ns, one tick = 666664 ps&lt;/p&gt;
&lt;p&gt;clamp:        maxcnt - 1        = 639 ns
       ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick
       tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns&lt;/p&gt;
&lt;p&gt;667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.&lt;/p&gt;
&lt;p&gt;Return early if timestamp_base is 0 (the unknown-crystal path).
Do the conversions in u64 via the *_ULL() helpers so they cannot wrap.
Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays
strictly below maxcn…&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;drm/xe: harden adjust_idledly() against divide-by-zero and overflow&lt;/p&gt;
&lt;p&gt;adjust_idledly() has several corner-case issues flagged during review:&lt;/p&gt;
&lt;p&gt;1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.
     The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a
     divide-by-zero and panics the kernel.&lt;/p&gt;
&lt;p&gt;2. The tick-to-ns conversions are done in u32:
        idledly * idledly_units_ps, (maxcnt - 1) * 1000
     Both overflow u32 before DIV_ROUND_CLOSEST() sees them.&lt;/p&gt;
&lt;p&gt;3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.&lt;/p&gt;
&lt;p&gt;4. The register only stores whole ticks, so the clamped ns value has
     to be converted to ticks and back. DIV_ROUND_CLOSEST() can round
     that conversion up past maxcnt:&lt;/p&gt;
&lt;p&gt;maxcnt = 640 ns, one tick = 666664 ps&lt;/p&gt;
&lt;p&gt;clamp:        maxcnt - 1        = 639 ns
       ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick
       tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns&lt;/p&gt;
&lt;p&gt;667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.&lt;/p&gt;
&lt;p&gt;Return early if timestamp_base is 0 (the unknown-crystal path).
Do the conversions in u64 via the *_ULL() helpers so they cannot wrap.
Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays
strictly below maxcn…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98919</guid>
    </item>
    <item>
      <title>GHSA-wghv-7vwx-fc47</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wghv-7vwx-fc47</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe: harden adjust_idledly() against divide-by-zero and overflow&lt;/p&gt;
&lt;p&gt;adjust_idledly() has several corner-case issues flagged during review:&lt;/p&gt;
&lt;p&gt;1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.
     The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a
     divide-by-zero and panics the kernel.&lt;/p&gt;
&lt;p&gt;2. The tick-to-ns conversions are done in u32:
        idledly * idledly_units_ps, (maxcnt - 1) * 1000
     Both overflow u32 before DIV_ROUND_CLOSEST() sees them.&lt;/p&gt;
&lt;p&gt;3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.&lt;/p&gt;
&lt;p&gt;4. The register only stores whole ticks, so the clamped ns value has
     to be converted to ticks and back. DIV_ROUND_CLOSEST() can round
     that conversion up past maxcnt:&lt;/p&gt;
&lt;p&gt;maxcnt = 640 ns, one tick = 666664 ps&lt;/p&gt;
&lt;p&gt;clamp:        maxcnt - 1        = 639 ns
       ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick
       tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns&lt;/p&gt;
&lt;p&gt;667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.&lt;/p&gt;
&lt;p&gt;Return early if timestamp_base is 0 (the unknown-crystal path).
Do the conversions in u64 via the *_ULL() helpers so they cannot wrap.
Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays
strictly below maxcn…&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;drm/xe: harden adjust_idledly() against divide-by-zero and overflow&lt;/p&gt;
&lt;p&gt;adjust_idledly() has several corner-case issues flagged during review:&lt;/p&gt;
&lt;p&gt;1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.
     The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a
     divide-by-zero and panics the kernel.&lt;/p&gt;
&lt;p&gt;2. The tick-to-ns conversions are done in u32:
        idledly * idledly_units_ps, (maxcnt - 1) * 1000
     Both overflow u32 before DIV_ROUND_CLOSEST() sees them.&lt;/p&gt;
&lt;p&gt;3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.&lt;/p&gt;
&lt;p&gt;4. The register only stores whole ticks, so the clamped ns value has
     to be converted to ticks and back. DIV_ROUND_CLOSEST() can round
     that conversion up past maxcnt:&lt;/p&gt;
&lt;p&gt;maxcnt = 640 ns, one tick = 666664 ps&lt;/p&gt;
&lt;p&gt;clamp:        maxcnt - 1        = 639 ns
       ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick
       tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns&lt;/p&gt;
&lt;p&gt;667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.&lt;/p&gt;
&lt;p&gt;Return early if timestamp_base is 0 (the unknown-crystal path).
Do the conversions in u64 via the *_ULL() helpers so they cannot wrap.
Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays
strictly below maxcn…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wghv-7vwx-fc47</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-98919 — drm/xe: harden adjust_idledly() against divide-by-zero and overflow</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98919</link>
      <description>msrc_CVE-2026-98919</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-98919</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98919</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98919</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: harden adjust_idledly() against divide-by-zero and overflow adjust_idledly() has several corner-case issues flagged during review:   1. If xe_gt_clock_init() failed to recognise the crystal clock,      gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.      The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a      divide-by-zero and panics the kernel.   2. The tick-to-ns conversions are done in u32:         idledly * idledly_units_ps, (maxcnt - 1) * 1000      Both overflow u32 before DIV_ROUND_CLOSEST() sees them.   3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and      the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.   4. The register only stores whole ticks, so the clamped ns value has      to be converted to ticks and back. DIV_ROUND_CLOSEST() can round      that conversion up past maxcnt:        maxcnt = 640 ns, one tick = 666664 ps        clamp:        maxcnt - 1        = 639 ns        ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick        tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns      667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),      so xe_gt_WARN_ON() fires again on every subsequent init. Return early if timestamp_base is 0 (the unknown-crystal path). Do the conversions in u64 via the *_ULL() helpers so they cannot wrap. Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays strictly below maxcnt, and gua…&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/xe: harden adjust_idledly() against divide-by-zero and overflow adjust_idledly() has several corner-case issues flagged during review:   1. If xe_gt_clock_init() failed to recognise the crystal clock,      gt-&amp;gt;info.timestamp_base is 0, which makes idledly_units_ps also 0.      The subsequent DIV_ROUND_CLOSEST(..., idledly_units_ps) is then a      divide-by-zero and panics the kernel.   2. The tick-to-ns conversions are done in u32:         idledly * idledly_units_ps, (maxcnt - 1) * 1000      Both overflow u32 before DIV_ROUND_CLOSEST() sees them.   3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and      the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.   4. The register only stores whole ticks, so the clamped ns value has      to be converted to ticks and back. DIV_ROUND_CLOSEST() can round      that conversion up past maxcnt:        maxcnt = 640 ns, one tick = 666664 ps        clamp:        maxcnt - 1        = 639 ns        ns -&amp;gt; ticks:  639000 / 666664   = 0.958 -&amp;gt; rounds to 1 tick        tick -&amp;gt; ns:    1 * 666664 / 1000 = 667 ns      667 ns is programmed into RING_IDLEDLY, but 667 &amp;gt;= maxcnt (640),      so xe_gt_WARN_ON() fires again on every subsequent init. Return early if timestamp_base is 0 (the unknown-crystal path). Do the conversions in u64 via the *_ULL() helpers so they cannot wrap. Clamp with a floor (DIV_ROUND_DOWN_ULL) so the programmed delay stays strictly below maxcnt, and gua…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98919</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
