From: "whyshall" <whyshall.dev@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: Urgent: Regarding Fixing of Security Vulnerabilities
Date: Mon, 13 Jul 2026 22:10:32 -0700 [thread overview]
Message-ID: <606502.1784005832694212955@lists.cip-project.org> (raw)
In-Reply-To: <alVT63ojQwHf4n7f@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 2947 bytes --]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------On Tue, Jul 14, 2026 at 02:39 AM, Pavel Machek wrote:
>
> 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.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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 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-sec.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 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* ?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 3592 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "whyshall" <whyshall.dev@gmail.com>
To: cip-dev@lists.cip-project.org
Subject: Re: Urgent: Regarding Fixing of Security Vulnerabilities
Date: Tue, 14 Jul 2026 00:48:46 -0700 [thread overview]
Message-ID: <606502.1784005832694212955@lists.cip-project.org> (raw)
Message-ID: <20260714074846.H9Mag7Ymi8B1djlVrNHORJlknNMdi7f_-Q7sh_o5p3Q@z> (raw)
In-Reply-To: <alVT63ojQwHf4n7f@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 2941 bytes --]
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------On Tue, Jul 14, 2026 at 02:39 AM, Pavel Machek wrote:
>
> 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.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> 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 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-sec.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/linux-cip.git ) in *linux-4.19.y-cip branch* ?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 3473 bytes --]
next prev parent reply other threads:[~2026-07-14 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 4:53 Urgent: Regarding Fixing of Security Vulnerabilities whyshall
2026-07-09 9:13 ` whyshall.dev
[not found] ` <Groupsio.1.CAOksrezPuEAoJ86FHMS_ajoH0h7pe3usksyo84n5rF9RKHfu4g@mail.gmail.com>
2026-07-13 21:08 ` [cip-dev] " Pavel Machek
2026-07-14 5:10 ` whyshall [this message]
2026-07-14 7:48 ` whyshall
2026-07-16 10:48 ` whyshall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=606502.1784005832694212955@lists.cip-project.org \
--to=whyshall.dev@gmail.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox