From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF843C43458 for ; Tue, 14 Jul 2026 05:10:41 +0000 (UTC) Subject: Re: Urgent: Regarding Fixing of Security Vulnerabilities To: cip-dev@lists.cip-project.org From: "whyshall" X-Originating-Location: IN (196.1.111.120) X-Originating-Platform: Linux Chrome 149 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Mon, 13 Jul 2026 22:10:32 -0700 References: In-Reply-To: Message-ID: <606502.1784005832694212955@lists.cip-project.org> Content-Type: multipart/alternative; boundary="QNW1Is1c48dIGdMg7Yn9" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 14 Jul 2026 05:10:41 -0000 X-Groupsio-URL: https://lists.cip-project.org/g/cip-dev/message/23570 --QNW1Is1c48dIGdMg7Yn9 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------On Tue, Jul 14, 2026 at 02:39 AM, Pavel Mach= ek wrote: >=20 > Would you mind introducing yourself, your company, and your product? > - This is Vishal Maheshwari (Senior Research Engineer) from Center for > Development of Telematics, Delhi, working on an embedded product based on > Linux kernel 4.19.94. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- >=20 > Normally, we would recommend 6.12 kernel branch if you are doing the > migration, anyway. - Can't port to this kernel as the driver support for a particular device i= n our board based on *Linux Kernel* *4.19.94* is missing in the *6.12.x* ke= rnel and don't have the *expertise* to port the *driver(s)* to the *6.12.x = series*. So,=C2=A0 can upgrade to *linux-cip-4.19.325-cipX* kernel only. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- >=20 > Take a look at > git@...:cip-project/cip-kernel/cip-kernel-sec.git . Ok, will try to run this tool. Would this tool be able to list out *the sol= ved and unsolved vulnerabilities* in *linux-cip-4.19.325-cipX* based on the= *.config file* modified as per our board ? ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- Also, will the CIP community not be solving all the vulnerabilities associa= ted with the *4.19.325* reported by websites like cve.org, cvedetails.com, = NVD databse etc in their repository *linux-cip* (repo link:- https://gitlab= .com/cip-project/cip-kernel/linux-cip.git ) in *linux-4.19.y-cip branch* ? ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------ --QNW1Is1c48dIGdMg7Yn9 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

---------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------On Tue, Jul 14, 2026 at 02:39 AM, Pavel Machek wrote:

Would you mind introducing yourself, your company, and your pro= duct?
 - This is Vishal Maheshwari (Senior Research Engineer) fro= m Center for Development of Telematics, Delhi, working on an embedded produ= ct based on Linux kernel 4.19.94.  

------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------

Normally, we would recommend 6.12 kernel branch if you are doin= g the
migration, anyway.

- Can't port to this kernel as the driver = support for a particular device in our board based on Linux Kernel<= /strong> 4.19.94 is missing in the 6.12.x= kernel and don't have the expertise to port the d= river(s) to the 6.12.x series. So,  can upgr= ade to linux-cip-4.19.325-cipX kernel only.

------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------

Take a look at
git@...:cip-project/cip-kernel/cip-kernel-s= ec.git .

Ok, will try to run this tool. Would this = tool be able to list out the solved and unsolved vulnerabilities in  linux-cip-4.19.325-cipX based on the .config file modified as per our board ?

------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------------------------------------

Also, will the CIP community not be solving all the vulnerabilities associ= ated with the 4.19.325 reported by websites like cve.o= rg, cvedetails.com, NVD databse etc in their repository linux-= cip(repo link:- https://gitlab.com/cip= -project/cip-kernel/linux-cip.git) in linux-4.19.y-cip branch <= /strong>?
--------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------------------

 

--QNW1Is1c48dIGdMg7Yn9-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2683EC43458 for ; Tue, 14 Jul 2026 07:49:04 +0000 (UTC) Subject: Re: Urgent: Regarding Fixing of Security Vulnerabilities To: cip-dev@lists.cip-project.org From: "whyshall" X-Originating-Location: IN (196.1.111.120) X-Originating-Platform: Linux Chrome 149 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Tue, 14 Jul 2026 00:48:46 -0700 References: In-Reply-To: Message-ID: <606502.1784005832694212955@lists.cip-project.org> X-Old-Date: Mon, 13 Jul 2026 22:10:32 -0700 Content-Type: multipart/alternative; boundary="QNW1Is1c48dIGdMg7Yn9" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 14 Jul 2026 07:49:04 -0000 X-Groupsio-URL: https://lists.cip-project.org/g/cip-dev/message/23570 Message-ID: <20260714074846.H9Mag7Ymi8B1djlVrNHORJlknNMdi7f_-Q7sh_o5p3Q@z> --QNW1Is1c48dIGdMg7Yn9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------On Tue, Jul 14, 2026 at 02:39 AM, Pavel Mach= ek wrote: >=20 > Would you mind introducing yourself, your company, and your product? > - This is Vishal Maheshwari (Senior Research Engineer) from Center for > Development of Telematics, Delhi, working on an embedded product based on > Linux kernel 4.19.94. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- >=20 > Normally, we would recommend 6.12 kernel branch if you are doing the > migration, anyway. - Can't port to this kernel as the driver support for a particular device i= n our board based on *Linux Kernel* *4.19.94* is missing in the *6.12.x* ke= rnel and don't have the *expertise* to port the *driver(s)* to the *6.12.x = series*. So,=C2=A0 can upgrade to *linux-cip-4.19.325-cipX* kernel only. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- >=20 > Take a look at > git@...:cip-project/cip-kernel/cip-kernel-sec.git . Ok, will try to run this tool. Would this tool be able to list out *the sol= ved and unsolved vulnerabilities* in *linux-cip-4.19.325-cipX* based on the= *.config file* modified as per our board ? ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------------- Also, will the CIP community not be solving all the vulnerabilities associa= ted with the *4.19.325* reported by websites like cve.org, cvedetails.com, = NVD=C2=A0 etc in their repository *linux-cip* (repo link:- https://gitlab.c= om/cip-project/cip-kernel/linux-cip.git ) in *linux-4.19.y-cip branch* ? ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------------ --QNW1Is1c48dIGdMg7Yn9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

-------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------On Tue, Jul = 14, 2026 at 02:39 AM, Pavel Machek wrote:

Would you mind introducing yourself, your company, and your pro= duct?
 - This is Vishal Maheshwari (Senior Research Engineer) fro= m Center for Development of Telematics, Delhi, working on an embedded produ= ct based on Linux kernel 4.19.94.  

------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------

Normally, we would recommend 6.12 kernel branch if you are doin= g the
migration, anyway.

- Can't port to this kernel as the driver support for a particular devic= e in our board based on Linux Kernel 4.19.94 is missing in the 6.12.x kernel and don't have the expertise to port the driver(s) to the 6.12.x series. So,  can upgrade to linux-cip-4.19.= 325-cipX kernel only.

------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------

Take a look at
git@...:cip-project/cip-kernel/cip-kernel-s= ec.git .

Ok, will try to run this tool. Would this tool be able to list out the solved and unsolved vulnerabilities in  linux-= cip-4.19.325-cipX based on the .config file = modified as per our board ?

------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ----------------------------------

Also, will the CIP community = not be solving all the vulnerabilities associated with the 4.19.325= reported by websites like cve.org, cvedetails.com, NVD  = etc in their repository linux-cip(repo link:- https://gitlab.com/cip-project/cip-kernel/lin= ux-cip.git) in linux-4.19.y-cip branch ?
----= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= --------------------

 

--QNW1Is1c48dIGdMg7Yn9--