<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックHow to fix CVE bugs in NXP kernel (and uboot) version</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-to-fix-CVE-bugs-in-NXP-kernel-and-uboot-version/m-p/1450564#M189804</link>
    <description>&lt;P&gt;De community:&lt;/P&gt;&lt;P&gt;Our embeded product information: iMX6UL + BSP-4.1.15_1.0.0&lt;/P&gt;&lt;P&gt;Question:&lt;/P&gt;&lt;P&gt;We need to pass the Security certificate of software. There are more than 700 CVE bugs in our v4.1.15 NXP kernel which is scaned by Black Duck.&lt;/P&gt;&lt;P&gt;1. Could we use the upstream new LTS kernel (from &lt;A href="http://www.kernel.org" target="_blank" rel="noopener"&gt;www.kernel.org&lt;/A&gt;) version (&lt;EM&gt;&lt;SPAN class=""&gt;&lt;A target="_blank"&gt;for&lt;/A&gt; &lt;A target="_blank"&gt;example&lt;/A&gt;&lt;/SPAN&gt;&lt;/EM&gt;: v4.19.240) directly on imx6ul soc, yes or no?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wheather or not the NXP have pushed all the imx6ul (or imx6 series) haredware related codes to the upstream kernel (include bug fix)?&lt;/P&gt;&lt;P&gt;Because there are minimum CVE bugs in the upstream new LTS version. It is difficult to backport the bug fix to the old v4.1.15 kernel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Or We have to upgrade to the new NXP kernel version (for example: v5.10.72_2.2.0), But that means we have to upgrade the kernel version regularly.&lt;/P&gt;&lt;P&gt;NXP upgrade just 2 or 3 versions on a major kernel, then go to next new major version of kernel (&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.62_1.0.0 -&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.78_1.0.0&amp;nbsp; -&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.98_2.0.0&amp;nbsp; &amp;nbsp;=&amp;gt;&amp;gt;&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;FONT color="#3366FF"&gt;4.19&lt;/FONT&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;35_1.1.0&lt;/SPAN&gt;). You know, it is also difficult to upgrade kernel version on embeded product regularly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any &lt;SPAN class=""&gt;constructive&lt;/SPAN&gt; suggest?&lt;/P&gt;&lt;P&gt;Thanks anyway !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Apr 2022 09:09:45 GMT</pubDate>
    <dc:creator>yunyangsihai</dc:creator>
    <dc:date>2022-04-28T09:09:45Z</dc:date>
    <item>
      <title>How to fix CVE bugs in NXP kernel (and uboot) version</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-fix-CVE-bugs-in-NXP-kernel-and-uboot-version/m-p/1450564#M189804</link>
      <description>&lt;P&gt;De community:&lt;/P&gt;&lt;P&gt;Our embeded product information: iMX6UL + BSP-4.1.15_1.0.0&lt;/P&gt;&lt;P&gt;Question:&lt;/P&gt;&lt;P&gt;We need to pass the Security certificate of software. There are more than 700 CVE bugs in our v4.1.15 NXP kernel which is scaned by Black Duck.&lt;/P&gt;&lt;P&gt;1. Could we use the upstream new LTS kernel (from &lt;A href="http://www.kernel.org" target="_blank" rel="noopener"&gt;www.kernel.org&lt;/A&gt;) version (&lt;EM&gt;&lt;SPAN class=""&gt;&lt;A target="_blank"&gt;for&lt;/A&gt; &lt;A target="_blank"&gt;example&lt;/A&gt;&lt;/SPAN&gt;&lt;/EM&gt;: v4.19.240) directly on imx6ul soc, yes or no?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wheather or not the NXP have pushed all the imx6ul (or imx6 series) haredware related codes to the upstream kernel (include bug fix)?&lt;/P&gt;&lt;P&gt;Because there are minimum CVE bugs in the upstream new LTS version. It is difficult to backport the bug fix to the old v4.1.15 kernel.&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. Or We have to upgrade to the new NXP kernel version (for example: v5.10.72_2.2.0), But that means we have to upgrade the kernel version regularly.&lt;/P&gt;&lt;P&gt;NXP upgrade just 2 or 3 versions on a major kernel, then go to next new major version of kernel (&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.62_1.0.0 -&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.78_1.0.0&amp;nbsp; -&amp;gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#3366FF"&gt;&lt;SPAN class=""&gt;4.14&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;.98_2.0.0&amp;nbsp; &amp;nbsp;=&amp;gt;&amp;gt;&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class=""&gt;&lt;FONT color="#3366FF"&gt;4.19&lt;/FONT&gt;.&lt;/SPAN&gt;&lt;SPAN&gt;35_1.1.0&lt;/SPAN&gt;). You know, it is also difficult to upgrade kernel version on embeded product regularly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any &lt;SPAN class=""&gt;constructive&lt;/SPAN&gt; suggest?&lt;/P&gt;&lt;P&gt;Thanks anyway !&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 09:09:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-fix-CVE-bugs-in-NXP-kernel-and-uboot-version/m-p/1450564#M189804</guid>
      <dc:creator>yunyangsihai</dc:creator>
      <dc:date>2022-04-28T09:09:45Z</dc:date>
    </item>
  </channel>
</rss>

