<?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>Mon, 05 Oct 2026 23:25:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52598 — s390/ptrace: handle setting of fpc register correctly</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-52598</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;s390/ptrace: handle setting of fpc register correctly&lt;/p&gt;
&lt;p&gt;If the content of the floating point control (fpc) register of a traced
process is modified with the ptrace interface the new value is tested for
validity by temporarily loading it into the fpc register.&lt;/p&gt;
&lt;p&gt;This may lead to corruption of the fpc register of the tracing process:
if an interrupt happens while the value is temporarily loaded into the
fpc register, and within interrupt context floating point or vector
registers are used, the current fp/vx registers are saved with
save_fpu_regs() assuming they belong to user space and will be loaded into
fp/vx registers when returning to user space.&lt;/p&gt;
&lt;p&gt;test_fp_ctl() restores the original user space fpc register value, however
it will be discarded, when returning to user space.&lt;/p&gt;
&lt;p&gt;In result the tracer will incorrectly continue to run with the value that
was supposed to be used for the traced process.&lt;/p&gt;
&lt;p&gt;Fix this by saving fpu register contents with save_fpu_regs() before using
test_fp_ctl().&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;s390/ptrace: handle setting of fpc register correctly&lt;/p&gt;
&lt;p&gt;If the content of the floating point control (fpc) register of a traced
process is modified with the ptrace interface the new value is tested for
validity by temporarily loading it into the fpc register.&lt;/p&gt;
&lt;p&gt;This may lead to corruption of the fpc register of the tracing process:
if an interrupt happens while the value is temporarily loaded into the
fpc register, and within interrupt context floating point or vector
registers are used, the current fp/vx registers are saved with
save_fpu_regs() assuming they belong to user space and will be loaded into
fp/vx registers when returning to user space.&lt;/p&gt;
&lt;p&gt;test_fp_ctl() restores the original user space fpc register value, however
it will be discarded, when returning to user space.&lt;/p&gt;
&lt;p&gt;In result the tracer will incorrectly continue to run with the value that
was supposed to be used for the traced process.&lt;/p&gt;
&lt;p&gt;Fix this by saving fpu register contents with save_fpu_regs() before using
test_fp_ctl().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-52598</guid>
    </item>
  </channel>
</rss>
