<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:35:39.058514+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-98919</id>
    <title>BELL-CVE-2026-98919</title>
    <updated>2026-11-17T10:35:39.069797+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-98919"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469</id>
    <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>
    <updated>2026-11-17T10:35:39.069859+00:00</updated>
    <content>certfr-2026-avi-1469</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1469"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-391517</id>
    <title>EUVD-2026-391517</title>
    <updated>2026-11-17T10:35:39.069881+00:00</updated>
    <content>EUVD-2026-391517</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-391517"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98919</id>
    <title>fkie_cve-2026-98919</title>
    <updated>2026-11-17T10:35:39.069907+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/xe: harden adjust_idledly() against divide-by-zero and overflow</p>
<p>adjust_idledly() has several corner-case issues flagged during review:</p>
<p>1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&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.</p>
<p>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.</p>
<p>3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.</p>
<p>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:</p>
<p>maxcnt = 640 ns, one tick = 666664 ps</p>
<p>clamp:        maxcnt - 1        = 639 ns
       ns -&gt; ticks:  639000 / 666664   = 0.958 -&gt; rounds to 1 tick
       tick -&gt; ns:    1 * 666664 / 1000 = 667 ns</p>
<p>667 ns is programmed into RING_IDLEDLY, but 667 &gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-98919"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wghv-7vwx-fc47</id>
    <title>GHSA-wghv-7vwx-fc47</title>
    <updated>2026-11-17T10:35:39.070007+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/xe: harden adjust_idledly() against divide-by-zero and overflow</p>
<p>adjust_idledly() has several corner-case issues flagged during review:</p>
<p>1. If xe_gt_clock_init() failed to recognise the crystal clock,
     gt-&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.</p>
<p>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.</p>
<p>3. If IDLE_WAIT_TIME reads back as 0, maxcnt evaluates to 0 and
     the maxcnt - 1 clamp wraps to 0xFFFFFFFF in u32.</p>
<p>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:</p>
<p>maxcnt = 640 ns, one tick = 666664 ps</p>
<p>clamp:        maxcnt - 1        = 639 ns
       ns -&gt; ticks:  639000 / 666664   = 0.958 -&gt; rounds to 1 tick
       tick -&gt; ns:    1 * 666664 / 1000 = 667 ns</p>
<p>667 ns is programmed into RING_IDLEDLY, but 667 &gt;= maxcnt (640),
     so xe_gt_WARN_ON() fires again on every subsequent init.</p>
<p>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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wghv-7vwx-fc47"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-98919</id>
    <title>msrc_CVE-2026-98919 — drm/xe: harden adjust_idledly() against divide-by-zero and overflow</title>
    <updated>2026-11-17T10:35:39.070087+00:00</updated>
    <content>msrc_CVE-2026-98919</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-98919"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98919</id>
    <title>UBUNTU-CVE-2026-98919</title>
    <updated>2026-11-17T10:35:39.070119+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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-&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 -&gt; ticks:  639000 / 666664   = 0.958 -&gt; rounds to 1 tick        tick -&gt; ns:    1 * 666664 / 1000 = 667 ns      667 ns is programmed into RING_IDLEDLY, but 667 &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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98919"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</id>
    <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T10:35:39.070516+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152"/>
  </entry>
</feed>
