<?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>Fri, 09 Oct 2026 03:43:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49924 — fbdev: pxafb: Fix possible use after free in pxafb_task()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-49924</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;fbdev: pxafb: Fix possible use after free in pxafb_task()&lt;/p&gt;
&lt;p&gt;In the pxafb_probe function, it calls the pxafb_init_fbinfo function,
after which &amp;amp;fbi-&amp;gt;task is associated with pxafb_task. Moreover,
within this pxafb_init_fbinfo function, the pxafb_blank function
within the &amp;amp;pxafb_ops struct is capable of scheduling work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call pxafb_remove to make cleanup,
it will call unregister_framebuffer function which can call
do_unregister_framebuffer to free fbi-&amp;gt;fb through
put_fb_info(fb_info), while the work mentioned above will be used.
The sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                                CPU1&lt;/p&gt;
&lt;p&gt;| pxafb_task
pxafb_remove                       |
unregister_framebuffer(info)       |
do_unregister_framebuffer(fb_info) |
put_fb_info(fb_info)               |
// free fbi-&amp;gt;fb                    | set_ctrlr_state(fbi, state)
                                   | __pxafb_lcd_power(fbi, 0)
                                   | fbi-&amp;gt;lcd_power(on, &amp;amp;fbi-&amp;gt;fb.var)
                                   | //use fbi-&amp;gt;fb&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding
with the cleanup in pxafb_remove.&lt;/p&gt;
&lt;p&gt;Note that only root user can remove the driver at runtime.&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;fbdev: pxafb: Fix possible use after free in pxafb_task()&lt;/p&gt;
&lt;p&gt;In the pxafb_probe function, it calls the pxafb_init_fbinfo function,
after which &amp;amp;fbi-&amp;gt;task is associated with pxafb_task. Moreover,
within this pxafb_init_fbinfo function, the pxafb_blank function
within the &amp;amp;pxafb_ops struct is capable of scheduling work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call pxafb_remove to make cleanup,
it will call unregister_framebuffer function which can call
do_unregister_framebuffer to free fbi-&amp;gt;fb through
put_fb_info(fb_info), while the work mentioned above will be used.
The sequence of operations that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                                CPU1&lt;/p&gt;
&lt;p&gt;| pxafb_task
pxafb_remove                       |
unregister_framebuffer(info)       |
do_unregister_framebuffer(fb_info) |
put_fb_info(fb_info)               |
// free fbi-&amp;gt;fb                    | set_ctrlr_state(fbi, state)
                                   | __pxafb_lcd_power(fbi, 0)
                                   | fbi-&amp;gt;lcd_power(on, &amp;amp;fbi-&amp;gt;fb.var)
                                   | //use fbi-&amp;gt;fb&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding
with the cleanup in pxafb_remove.&lt;/p&gt;
&lt;p&gt;Note that only root user can remove the driver at runtime.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-49924</guid>
    </item>
  </channel>
</rss>
