kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Benjamin Selormey <cudjoe03@hotmail.com>
Cc: "kernelnewbies@kernelnewbies.org" <kernelnewbies@kernelnewbies.org>
Subject: Re: Just started w/Linux Kernel (Beginner)
Date: Sun, 24 Nov 2019 19:32:43 -0500	[thread overview]
Message-ID: <381769.1574641963@turing-police> (raw)
In-Reply-To: <VI1PR0701MB222318A3B48F4048004B5E57DE4B0@VI1PR0701MB2223.eurprd07.prod.outlook.com>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.1: Type: text/plain; charset=us-ascii, Size: 1133 bytes --]

On Sun, 24 Nov 2019 11:58:24 +0000, Benjamin Selormey said:
> Hello,
>
> I’m a newbie with Linux kernel and I l want to contribute in security research of  the Linux Kernel.

A newbie? Go and read https://lists.kernelnewbies.org/pipermail/kernelnewbies/2017-April/017765.html
and Documentation/process/submitting-patches.rst in your git tree.

You *do* have a git tree of some appropriate kernel, right? If not, fix that deficiency. :)

> I am interested in memory management and devices communication with the kernel. Does anyone have a starter project in mind I can start with?

Hmm.  Security and memory management? The obvious place to start is to go and
look at all the since-patched cases of vma splits and merges abused for
exploits. Google for 'vma bug linux'.  Read, understand, and look for other
similar issues. Note that you'll probably need to understand in sufficient
depth that you can write at least a PoC (proof of concept) exploit that
demonstrates the problem.

Note that you may have trouble finding anything, most of the obvious cases got
pointed out by Solar Designer and Brad Spengler a decade or more ago.


[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-11-25  0:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-24 11:58 Just started w/Linux Kernel (Beginner) Benjamin Selormey
2019-11-25  0:32 ` Valdis Klētnieks [this message]
2019-11-25  5:54   ` Benjamin Selormey

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=381769.1574641963@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=cudjoe03@hotmail.com \
    --cc=kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).