All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 252] Possible access to invalid FDs in rte_eth_tap
Date: Fri, 12 Apr 2019 16:58:53 +0000	[thread overview]
Message-ID: <bug-252-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=252

            Bug ID: 252
           Summary: Possible access to invalid FDs in rte_eth_tap
           Product: DPDK
           Version: 18.11
          Hardware: All
                OS: All
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: herakliusz.lipiec@intel.com
  Target Milestone: ---

In tap_mp_attach_queues function in rte_eth_tap.c we iterate over a queue of
fds received through IPC and we dont check if they are valid FDs before
assigning them to txq and rxq. There is also no check for number of received
messages (there could be none if IPC is disabled so checking of the return code
is not enough).
Present in 18.11, 19.02 and 19.05rc1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2019-04-12 16:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-252-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.