idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
158,696 | linux | 64f3b9e203bd06855072e295557dca1485a2ecba | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/64f3b9e203bd06855072e295557dca1485a2ecba | net: ip_expire() must revalidate route
Commit 4a94445c9a5c (net: Use ip_route_input_noref() in input path)
added a bug in IP defragmentation handling, in case timeout is fired.
When a frame is defragmented, we use last skb dst field when building
final skb. Its dst is valid, since we are in rcu read section.
But if ... | 0 | static void ip_expire(unsigned long arg)
{
struct ipq *qp;
struct net *net;
qp = container_of((struct inet_frag_queue *) arg, struct ipq, q);
net = container_of(qp->q.net, struct net, ipv4.frags);
spin_lock(&qp->q.lock);
if (qp->q.last_in & INET_FRAG_COMPLETE)
goto out;
ipq_kill(qp);
IP_INC_STATS_BH(net,... | 234,015,083,110,757,400,000,000,000,000,000,000,000 | ip_fragment.c | 88,100,855,803,852,200,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-1927 | The ip_expire function in net/ipv4/ip_fragment.c in the Linux kernel before 2.6.39 does not properly construct ICMP_TIME_EXCEEDED packets after a timeout, which allows remote attackers to cause a denial of service (invalid pointer dereference) via crafted fragmented packets. | https://nvd.nist.gov/vuln/detail/CVE-2011-1927 |
856 | linux | 764355487ea220fdc2faf128d577d7f679b91f97 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/764355487ea220fdc2faf128d577d7f679b91f97 | Ecryptfs: Add mount option to check uid of device being mounted = expect uid
Close a TOCTOU race for mounts done via ecryptfs-mount-private. The mount
source (device) can be raced when the ownership test is done in userspace.
Provide Ecryptfs a means to force the uid check at mount time.
Signed-off-by: John Johansen... | 1 | static struct dentry *ecryptfs_mount(struct file_system_type *fs_type, int flags,
const char *dev_name, void *raw_data)
{
struct super_block *s;
struct ecryptfs_sb_info *sbi;
struct ecryptfs_dentry_info *root_info;
const char *err = "Getting sb failed";
struct inode *inode;
struct path path;
int rc;
s... | 178,146,217,980,549,530,000,000,000,000,000,000,000 | main.c | 249,723,411,697,278,600,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-1833 | Race condition in the ecryptfs_mount function in fs/ecryptfs/main.c in the eCryptfs subsystem in the Linux kernel before 3.1 allows local users to bypass intended file permissions via a mount.ecryptfs_private mount with a mismatched uid. | https://nvd.nist.gov/vuln/detail/CVE-2011-1833 |
158,697 | linux | 764355487ea220fdc2faf128d577d7f679b91f97 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/764355487ea220fdc2faf128d577d7f679b91f97 | Ecryptfs: Add mount option to check uid of device being mounted = expect uid
Close a TOCTOU race for mounts done via ecryptfs-mount-private. The mount
source (device) can be raced when the ownership test is done in userspace.
Provide Ecryptfs a means to force the uid check at mount time.
Signed-off-by: John Johansen... | 0 | static struct dentry *ecryptfs_mount(struct file_system_type *fs_type, int flags,
const char *dev_name, void *raw_data)
{
struct super_block *s;
struct ecryptfs_sb_info *sbi;
struct ecryptfs_dentry_info *root_info;
const char *err = "Getting sb failed";
struct inode *inode;
struct path path;
uid_t check_ru... | 174,701,076,180,323,850,000,000,000,000,000,000,000 | main.c | 327,155,547,214,049,540,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-1833 | Race condition in the ecryptfs_mount function in fs/ecryptfs/main.c in the eCryptfs subsystem in the Linux kernel before 3.1 allows local users to bypass intended file permissions via a mount.ecryptfs_private mount with a mismatched uid. | https://nvd.nist.gov/vuln/detail/CVE-2011-1833 |
878 | linux | 43629f8f5ea32a998d06d1bb41eefa0e821ff573 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/43629f8f5ea32a998d06d1bb41eefa0e821ff573 | Bluetooth: bnep: fix buffer overflow
Struct ca is copied from userspace. It is not checked whether the "device"
field is NULL terminated. This potentially leads to BUG() inside of
alloc_netdev_mqs() and/or information leak by creating a device with a name
made of contents of kernel stack.
Signed-off-by: Vasiliy Kul... | 1 | static int bnep_sock_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
{
struct bnep_connlist_req cl;
struct bnep_connadd_req ca;
struct bnep_conndel_req cd;
struct bnep_conninfo ci;
struct socket *nsock;
void __user *argp = (void __user *)arg;
int err;
BT_DBG("cmd %x arg %lx", cmd, arg);
swi... | 245,883,328,951,772,840,000,000,000,000,000,000,000 | sock.c | 102,512,589,646,469,780,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-1079 | The bnep_sock_ioctl function in net/bluetooth/bnep/sock.c in the Linux kernel before 2.6.39 does not ensure that a certain device field ends with a '\0' character, which allows local users to obtain potentially sensitive information from kernel stack memory, or cause a denial of service (BUG and system crash), via a BN... | https://nvd.nist.gov/vuln/detail/CVE-2011-1079 |
158,714 | linux | 43629f8f5ea32a998d06d1bb41eefa0e821ff573 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/43629f8f5ea32a998d06d1bb41eefa0e821ff573 | Bluetooth: bnep: fix buffer overflow
Struct ca is copied from userspace. It is not checked whether the "device"
field is NULL terminated. This potentially leads to BUG() inside of
alloc_netdev_mqs() and/or information leak by creating a device with a name
made of contents of kernel stack.
Signed-off-by: Vasiliy Kul... | 0 | static int bnep_sock_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
{
struct bnep_connlist_req cl;
struct bnep_connadd_req ca;
struct bnep_conndel_req cd;
struct bnep_conninfo ci;
struct socket *nsock;
void __user *argp = (void __user *)arg;
int err;
BT_DBG("cmd %x arg %lx", cmd, arg);
swi... | 257,001,690,890,988,300,000,000,000,000,000,000,000 | sock.c | 202,386,133,395,416,600,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-1079 | The bnep_sock_ioctl function in net/bluetooth/bnep/sock.c in the Linux kernel before 2.6.39 does not ensure that a certain device field ends with a '\0' character, which allows local users to obtain potentially sensitive information from kernel stack memory, or cause a denial of service (BUG and system crash), via a BN... | https://nvd.nist.gov/vuln/detail/CVE-2011-1079 |
883 | linux | 6b0d6a9b4296fa16a28d10d416db7a770fc03287 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6b0d6a9b4296fa16a28d10d416db7a770fc03287 | bridge: Fix mglist corruption that leads to memory corruption
The list mp->mglist is used to indicate whether a multicast group
is active on the bridge interface itself as opposed to one of the
constituent interfaces in the bridge.
Unfortunately the operation that adds the mp->mglist node to the
list neglected to che... | 1 | static int br_multicast_add_group(struct net_bridge *br,
struct net_bridge_port *port,
struct br_ip *group)
{
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
unsigned long now = jiffies;
int err;
spin_lock(&br->multicast_lock);
if (!netif_ru... | 126,154,348,126,534,700,000,000,000,000,000,000,000 | br_multicast.c | 322,560,698,151,282,430,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2011-0716 | The br_multicast_add_group function in net/bridge/br_multicast.c in the Linux kernel before 2.6.38, when a certain Ethernet bridge configuration is used, allows local users to cause a denial of service (memory corruption and system crash) by sending IGMP packets to a local interface. | https://nvd.nist.gov/vuln/detail/CVE-2011-0716 |
158,719 | linux | 6b0d6a9b4296fa16a28d10d416db7a770fc03287 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6b0d6a9b4296fa16a28d10d416db7a770fc03287 | bridge: Fix mglist corruption that leads to memory corruption
The list mp->mglist is used to indicate whether a multicast group
is active on the bridge interface itself as opposed to one of the
constituent interfaces in the bridge.
Unfortunately the operation that adds the mp->mglist node to the
list neglected to che... | 0 | static int br_multicast_add_group(struct net_bridge *br,
struct net_bridge_port *port,
struct br_ip *group)
{
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
unsigned long now = jiffies;
int err;
spin_lock(&br->multicast_lock);
if (!netif_ru... | 13,316,443,721,025,886,000,000,000,000,000,000,000 | br_multicast.c | 98,479,723,134,747,550,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2011-0716 | The br_multicast_add_group function in net/bridge/br_multicast.c in the Linux kernel before 2.6.38, when a certain Ethernet bridge configuration is used, allows local users to cause a denial of service (memory corruption and system crash) by sending IGMP packets to a local interface. | https://nvd.nist.gov/vuln/detail/CVE-2011-0716 |
884 | linux | 867c20265459d30a01b021a9c1e81fb4c5832aa9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/867c20265459d30a01b021a9c1e81fb4c5832aa9 | ima: fix add LSM rule bug
If security_filter_rule_init() doesn't return a rule, then not everything
is as fine as the return code implies.
This bug only occurs when the LSM (eg. SELinux) is disabled at runtime.
Adding an empty LSM rule causes ima_match_rules() to always succeed,
ignoring any remaining rules.
defau... | 1 | static int ima_lsm_rule_init(struct ima_measure_rule_entry *entry,
char *args, int lsm_rule, int audit_type)
{
int result;
if (entry->lsm[lsm_rule].rule)
return -EINVAL;
entry->lsm[lsm_rule].type = audit_type;
result = security_filter_rule_init(entry->lsm[lsm_rule].type,
Audit_equal, args,
... | 289,210,770,505,321,260,000,000,000,000,000,000,000 | ima_policy.c | 269,496,230,888,596,200,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-0006 | The ima_lsm_rule_init function in security/integrity/ima/ima_policy.c in the Linux kernel before 2.6.37, when the Linux Security Modules (LSM) framework is disabled, allows local users to bypass Integrity Measurement Architecture (IMA) rules in opportunistic circumstances by leveraging an administrator's addition of an... | https://nvd.nist.gov/vuln/detail/CVE-2011-0006 |
158,720 | linux | 867c20265459d30a01b021a9c1e81fb4c5832aa9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/867c20265459d30a01b021a9c1e81fb4c5832aa9 | ima: fix add LSM rule bug
If security_filter_rule_init() doesn't return a rule, then not everything
is as fine as the return code implies.
This bug only occurs when the LSM (eg. SELinux) is disabled at runtime.
Adding an empty LSM rule causes ima_match_rules() to always succeed,
ignoring any remaining rules.
defau... | 0 | static int ima_lsm_rule_init(struct ima_measure_rule_entry *entry,
char *args, int lsm_rule, int audit_type)
{
int result;
if (entry->lsm[lsm_rule].rule)
return -EINVAL;
entry->lsm[lsm_rule].type = audit_type;
result = security_filter_rule_init(entry->lsm[lsm_rule].type,
Audit_equal, args,
... | 81,635,322,221,108,490,000,000,000,000,000,000,000 | ima_policy.c | 158,128,938,685,264,110,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2011-0006 | The ima_lsm_rule_init function in security/integrity/ima/ima_policy.c in the Linux kernel before 2.6.37, when the Linux Security Modules (LSM) framework is disabled, allows local users to bypass Integrity Measurement Architecture (IMA) rules in opportunistic circumstances by leveraging an administrator's addition of an... | https://nvd.nist.gov/vuln/detail/CVE-2011-0006 |
885 | linux | 7572777eef78ebdee1ecb7c258c0ef94d35bad16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7572777eef78ebdee1ecb7c258c0ef94d35bad16 | fuse: verify ioctl retries
Verify that the total length of the iovec returned in FUSE_IOCTL_RETRY
doesn't overflow iov_length().
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
CC: Tejun Heo <tj@kernel.org>
CC: <stable@kernel.org> [2.6.31+] | 1 | long fuse_do_ioctl(struct file *file, unsigned int cmd, unsigned long arg,
unsigned int flags)
{
struct fuse_file *ff = file->private_data;
struct fuse_conn *fc = ff->fc;
struct fuse_ioctl_in inarg = {
.fh = ff->fh,
.cmd = cmd,
.arg = arg,
.flags = flags
};
struct fuse_ioctl_out outarg;
struct fuse_r... | 265,577,904,395,187,430,000,000,000,000,000,000,000 | file.c | 190,320,006,487,793,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2010-4650 | Buffer overflow in the fuse_do_ioctl function in fs/fuse/file.c in the Linux kernel before 2.6.37 allows local users to cause a denial of service or possibly have unspecified other impact by leveraging the ability to operate a CUSE server. | https://nvd.nist.gov/vuln/detail/CVE-2010-4650 |
158,721 | linux | 7572777eef78ebdee1ecb7c258c0ef94d35bad16 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7572777eef78ebdee1ecb7c258c0ef94d35bad16 | fuse: verify ioctl retries
Verify that the total length of the iovec returned in FUSE_IOCTL_RETRY
doesn't overflow iov_length().
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
CC: Tejun Heo <tj@kernel.org>
CC: <stable@kernel.org> [2.6.31+] | 0 | long fuse_do_ioctl(struct file *file, unsigned int cmd, unsigned long arg,
unsigned int flags)
{
struct fuse_file *ff = file->private_data;
struct fuse_conn *fc = ff->fc;
struct fuse_ioctl_in inarg = {
.fh = ff->fh,
.cmd = cmd,
.arg = arg,
.flags = flags
};
struct fuse_ioctl_out outarg;
struct fuse_r... | 73,869,176,651,699,470,000,000,000,000,000,000,000 | file.c | 316,485,230,383,673,700,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2010-4650 | Buffer overflow in the fuse_do_ioctl function in fs/fuse/file.c in the Linux kernel before 2.6.37 allows local users to cause a denial of service or possibly have unspecified other impact by leveraging the ability to operate a CUSE server. | https://nvd.nist.gov/vuln/detail/CVE-2010-4650 |
888 | linux | f5563318ff1bde15b10e736e97ffce13be08bc1a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f5563318ff1bde15b10e736e97ffce13be08bc1a | wireless: radiotap: fix parsing buffer overrun
When parsing an invalid radiotap header, the parser can overrun
the buffer that is passed in because it doesn't correctly check
1) the minimum radiotap header size
2) the space for extended bitmaps
The first issue doesn't affect any in-kernel user as they all
check the... | 1 | int ieee80211_radiotap_iterator_init(
struct ieee80211_radiotap_iterator *iterator,
struct ieee80211_radiotap_header *radiotap_header,
int max_length, const struct ieee80211_radiotap_vendor_namespaces *vns)
{
/* Linux only supports version 0 radiotap format */
if (radiotap_header->it_version)
return -EINVA... | 202,083,656,134,031,100,000,000,000,000,000,000,000 | radiotap.c | 86,018,721,253,196,040,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7027 | The ieee80211_radiotap_iterator_init function in net/wireless/radiotap.c in the Linux kernel before 3.11.7 does not check whether a frame contains any data outside of the header, which might allow attackers to cause a denial of service (buffer over-read) via a crafted header. | https://nvd.nist.gov/vuln/detail/CVE-2013-7027 |
158,723 | linux | f5563318ff1bde15b10e736e97ffce13be08bc1a | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f5563318ff1bde15b10e736e97ffce13be08bc1a | wireless: radiotap: fix parsing buffer overrun
When parsing an invalid radiotap header, the parser can overrun
the buffer that is passed in because it doesn't correctly check
1) the minimum radiotap header size
2) the space for extended bitmaps
The first issue doesn't affect any in-kernel user as they all
check the... | 0 | int ieee80211_radiotap_iterator_init(
struct ieee80211_radiotap_iterator *iterator,
struct ieee80211_radiotap_header *radiotap_header,
int max_length, const struct ieee80211_radiotap_vendor_namespaces *vns)
{
/* check the radiotap header can actually be present */
if (max_length < sizeof(struct ieee80211_radiot... | 293,055,781,004,458,760,000,000,000,000,000,000,000 | radiotap.c | 23,121,824,623,036,653,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7027 | The ieee80211_radiotap_iterator_init function in net/wireless/radiotap.c in the Linux kernel before 3.11.7 does not check whether a frame contains any data outside of the header, which might allow attackers to cause a denial of service (buffer over-read) via a crafted header. | https://nvd.nist.gov/vuln/detail/CVE-2013-7027 |
893 | FFmpeg | f31011e9abfb2ae75bb32bc44e2c34194c8dc40a | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/f31011e9abfb2ae75bb32bc44e2c34194c8dc40a | avcodec/parser: reset indexes on realloc failure
Fixes Ticket2982
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | int ff_combine_frame(ParseContext *pc, int next, const uint8_t **buf, int *buf_size)
{
if(pc->overread){
av_dlog(NULL, "overread %d, state:%X next:%d index:%d o_index:%d\n",
pc->overread, pc->state, next, pc->index, pc->overread_index);
av_dlog(NULL, "%X %X %X %X\n", (*buf)[0], (*buf... | 222,309,056,610,865,200,000,000,000,000,000,000,000 | parser.c | 161,485,228,604,924,500,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7023 | The ff_combine_frame function in libavcodec/parser.c in FFmpeg before 2.1 does not properly handle certain memory-allocation errors, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7023 |
158,727 | FFmpeg | f31011e9abfb2ae75bb32bc44e2c34194c8dc40a | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/f31011e9abfb2ae75bb32bc44e2c34194c8dc40a | avcodec/parser: reset indexes on realloc failure
Fixes Ticket2982
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | int ff_combine_frame(ParseContext *pc, int next, const uint8_t **buf, int *buf_size)
{
if(pc->overread){
av_dlog(NULL, "overread %d, state:%X next:%d index:%d o_index:%d\n",
pc->overread, pc->state, next, pc->index, pc->overread_index);
av_dlog(NULL, "%X %X %X %X\n", (*buf)[0], (*buf... | 140,651,272,046,924,700,000,000,000,000,000,000,000 | parser.c | 105,227,933,394,977,880,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7023 | The ff_combine_frame function in libavcodec/parser.c in FFmpeg before 2.1 does not properly handle certain memory-allocation errors, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7023 |
894 | FFmpeg | e07ac727c1cc9eed39e7f9117c97006f719864bd | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e07ac727c1cc9eed39e7f9117c97006f719864bd | avcodec/g2meet: Fix framebuf size
Currently the code can in some cases draw tiles that hang outside the
allocated buffer. This patch increases the buffer size to avoid out
of array accesses. An alternative would be to fail if such tiles are
encountered.
I do not know if any valid files use such hanging tiles.
Fixes T... | 1 | static int g2m_init_buffers(G2MContext *c)
{
int aligned_height;
if (!c->framebuf || c->old_width < c->width || c->old_height < c->height) {
c->framebuf_stride = FFALIGN(c->width * 3, 16);
aligned_height = FFALIGN(c->height, 16);
av_free(c->framebuf);
c->framebuf = a... | 255,877,059,988,693,140,000,000,000,000,000,000,000 | g2meet.c | 290,068,666,600,478,200,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7022 | The g2m_init_buffers function in libavcodec/g2meet.c in FFmpeg before 2.1 does not properly allocate memory for tiles, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Go2Webinar data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7022 |
158,728 | FFmpeg | e07ac727c1cc9eed39e7f9117c97006f719864bd | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/e07ac727c1cc9eed39e7f9117c97006f719864bd | avcodec/g2meet: Fix framebuf size
Currently the code can in some cases draw tiles that hang outside the
allocated buffer. This patch increases the buffer size to avoid out
of array accesses. An alternative would be to fail if such tiles are
encountered.
I do not know if any valid files use such hanging tiles.
Fixes T... | 0 | static int g2m_init_buffers(G2MContext *c)
{
int aligned_height;
if (!c->framebuf || c->old_width < c->width || c->old_height < c->height) {
c->framebuf_stride = FFALIGN(c->width + 15, 16) * 3;
aligned_height = c->height + 15;
av_free(c->framebuf);
c->framebuf = av_mall... | 49,709,330,371,647,020,000,000,000,000,000,000,000 | g2meet.c | 165,207,066,110,261,870,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7022 | The g2m_init_buffers function in libavcodec/g2meet.c in FFmpeg before 2.1 does not properly allocate memory for tiles, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Go2Webinar data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7022 |
895 | FFmpeg | cdd5df8189ff1537f7abe8defe971f80602cc2d2 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/cdd5df8189ff1537f7abe8defe971f80602cc2d2 | avfilter/vf_fps: make sure the fifo is not empty before using it
Fixes Ticket2905
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static int filter_frame(AVFilterLink *inlink, AVFrame *buf)
{
AVFilterContext *ctx = inlink->dst;
FPSContext *s = ctx->priv;
AVFilterLink *outlink = ctx->outputs[0];
int64_t delta;
int i, ret;
s->frames_in++;
/* discard frames until we get the first timestamp */
if (s->pt... | 40,209,124,885,848,567,000,000,000,000,000,000,000 | vf_fps.c | 87,163,599,502,171,520,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7021 | The filter_frame function in libavfilter/vf_fps.c in FFmpeg before 2.1 does not properly ensure the availability of FIFO content, which allows remote attackers to cause a denial of service (double free) or possibly have unspecified other impact via crafted data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7021 |
158,729 | FFmpeg | cdd5df8189ff1537f7abe8defe971f80602cc2d2 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/cdd5df8189ff1537f7abe8defe971f80602cc2d2 | avfilter/vf_fps: make sure the fifo is not empty before using it
Fixes Ticket2905
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static int filter_frame(AVFilterLink *inlink, AVFrame *buf)
{
AVFilterContext *ctx = inlink->dst;
FPSContext *s = ctx->priv;
AVFilterLink *outlink = ctx->outputs[0];
int64_t delta;
int i, ret;
s->frames_in++;
/* discard frames until we get the first timestamp */
if (s->pt... | 117,732,054,672,985,900,000,000,000,000,000,000,000 | vf_fps.c | 201,548,077,166,799,530,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-7021 | The filter_frame function in libavfilter/vf_fps.c in FFmpeg before 2.1 does not properly ensure the availability of FIFO content, which allows remote attackers to cause a denial of service (double free) or possibly have unspecified other impact via crafted data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7021 |
896 | FFmpeg | b05cd1ea7e45a836f7f6071a716c38bb30326e0f | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/b05cd1ea7e45a836f7f6071a716c38bb30326e0f | ffv1dec: Check bits_per_raw_sample and colorspace for equality in ver 0/1 headers
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static int read_header(FFV1Context *f)
{
uint8_t state[CONTEXT_SIZE];
int i, j, context_count = -1; //-1 to avoid warning
RangeCoder *const c = &f->slice_context[0]->c;
memset(state, 128, sizeof(state));
if (f->version < 2) {
int chroma_planes, chroma_h_shift, chroma_v_shift, transparen... | 145,906,591,874,544,820,000,000,000,000,000,000,000 | ffv1dec.c | 84,436,554,014,232,130,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7020 | The read_header function in libavcodec/ffv1dec.c in FFmpeg before 2.1 does not properly enforce certain bit-count and colorspace constraints, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted FFV1 data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7020 |
158,730 | FFmpeg | b05cd1ea7e45a836f7f6071a716c38bb30326e0f | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/b05cd1ea7e45a836f7f6071a716c38bb30326e0f | ffv1dec: Check bits_per_raw_sample and colorspace for equality in ver 0/1 headers
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static int read_header(FFV1Context *f)
{
uint8_t state[CONTEXT_SIZE];
int i, j, context_count = -1; //-1 to avoid warning
RangeCoder *const c = &f->slice_context[0]->c;
memset(state, 128, sizeof(state));
if (f->version < 2) {
int chroma_planes, chroma_h_shift, chroma_v_shift, transparen... | 89,588,011,034,658,380,000,000,000,000,000,000,000 | ffv1dec.c | 319,230,643,551,834,150,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7020 | The read_header function in libavcodec/ffv1dec.c in FFmpeg before 2.1 does not properly enforce certain bit-count and colorspace constraints, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted FFV1 data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7020 |
902 | FFmpeg | 880c73cd76109697447fbfbaa8e5ee5683309446 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/880c73cd76109697447fbfbaa8e5ee5683309446 | avcodec/flashsv: check diff_start/height
Fixes out of array accesses
Fixes Ticket2844
Found-by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static int flashsv_decode_frame(AVCodecContext *avctx, void *data,
int *got_frame, AVPacket *avpkt)
{
int buf_size = avpkt->size;
FlashSVContext *s = avctx->priv_data;
int h_blocks, v_blocks, h_part, v_part, i, j, ret;
GetBitContext gb;
int last_blockwidth = s-... | 269,767,046,134,726,600,000,000,000,000,000,000,000 | flashsv.c | 325,814,377,149,258,860,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7015 | The flashsv_decode_frame function in libavcodec/flashsv.c in FFmpeg before 2.1 does not properly validate a certain height value, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Flash Screen Video data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7015 |
158,732 | FFmpeg | 880c73cd76109697447fbfbaa8e5ee5683309446 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/880c73cd76109697447fbfbaa8e5ee5683309446 | avcodec/flashsv: check diff_start/height
Fixes out of array accesses
Fixes Ticket2844
Found-by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static int flashsv_decode_frame(AVCodecContext *avctx, void *data,
int *got_frame, AVPacket *avpkt)
{
int buf_size = avpkt->size;
FlashSVContext *s = avctx->priv_data;
int h_blocks, v_blocks, h_part, v_part, i, j, ret;
GetBitContext gb;
int last_blockwidth = s-... | 194,696,856,989,091,400,000,000,000,000,000,000,000 | flashsv.c | 135,631,529,426,881,730,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-7015 | The flashsv_decode_frame function in libavcodec/flashsv.c in FFmpeg before 2.1 does not properly validate a certain height value, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Flash Screen Video data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7015 |
903 | FFmpeg | 86736f59d6a527d8bc807d09b93f971c0fe0bb07 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/86736f59d6a527d8bc807d09b93f971c0fe0bb07 | avcodec/pngdsp: fix (un)signed type in end comparission
Fixes out of array accesses
Fixes Ticket2919
Found_by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static void add_bytes_l2_c(uint8_t *dst, uint8_t *src1, uint8_t *src2, int w)
{
long i;
for (i = 0; i <= w - sizeof(long); i += sizeof(long)) {
long a = *(long *)(src1 + i);
long b = *(long *)(src2 + i);
*(long *)(dst + i) = ((a & pb_7f) + (b & pb_7f)) ^ ((a ^ b) & pb_80);
}
... | 13,327,716,502,808,840,000,000,000,000,000,000,000 | pngdsp.c | 272,561,586,882,969,750,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-7014 | Integer signedness error in the add_bytes_l2_c function in libavcodec/pngdsp.c in FFmpeg before 2.1 allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted PNG data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7014 |
158,733 | FFmpeg | 86736f59d6a527d8bc807d09b93f971c0fe0bb07 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/86736f59d6a527d8bc807d09b93f971c0fe0bb07 | avcodec/pngdsp: fix (un)signed type in end comparission
Fixes out of array accesses
Fixes Ticket2919
Found_by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static void add_bytes_l2_c(uint8_t *dst, uint8_t *src1, uint8_t *src2, int w)
{
long i;
for (i = 0; i <= w - (int)sizeof(long); i += sizeof(long)) {
long a = *(long *)(src1 + i);
long b = *(long *)(src2 + i);
*(long *)(dst + i) = ((a & pb_7f) + (b & pb_7f)) ^ ((a ^ b) & pb_80);
... | 132,338,722,680,055,210,000,000,000,000,000,000,000 | pngdsp.c | 77,830,949,276,076,410,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-7014 | Integer signedness error in the add_bytes_l2_c function in libavcodec/pngdsp.c in FFmpeg before 2.1 allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted PNG data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7014 |
905 | FFmpeg | 780669ef7c23c00836a24921fcc6b03be2b8ca4a | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/780669ef7c23c00836a24921fcc6b03be2b8ca4a | avcodec/jpeg2000dec: non zero image offsets are not supported
Fixes out of array accesses
Fixes Ticket3080
Found-by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static int get_siz(Jpeg2000DecoderContext *s)
{
int i;
int ncomponents;
uint32_t log2_chroma_wh = 0;
const enum AVPixelFormat *possible_fmts = NULL;
int possible_fmts_nb = 0;
if (bytestream2_get_bytes_left(&s->g) < 36)
return AVERROR_INVALIDDATA;
s->avctx->profile = bytestream2_get... | 85,678,138,236,663,390,000,000,000,000,000,000,000 | jpeg2000dec.c | 302,431,616,552,773,530,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7012 | The get_siz function in libavcodec/jpeg2000dec.c in FFmpeg before 2.1 does not prevent attempts to use non-zero image offsets, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted JPEG2000 data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7012 |
158,734 | FFmpeg | 780669ef7c23c00836a24921fcc6b03be2b8ca4a | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/780669ef7c23c00836a24921fcc6b03be2b8ca4a | avcodec/jpeg2000dec: non zero image offsets are not supported
Fixes out of array accesses
Fixes Ticket3080
Found-by: ami_stuff
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static int get_siz(Jpeg2000DecoderContext *s)
{
int i;
int ncomponents;
uint32_t log2_chroma_wh = 0;
const enum AVPixelFormat *possible_fmts = NULL;
int possible_fmts_nb = 0;
if (bytestream2_get_bytes_left(&s->g) < 36)
return AVERROR_INVALIDDATA;
s->avctx->profile = bytestream2_get... | 111,165,660,664,067,900,000,000,000,000,000,000,000 | jpeg2000dec.c | 223,101,191,426,622,220,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7012 | The get_siz function in libavcodec/jpeg2000dec.c in FFmpeg before 2.1 does not prevent attempts to use non-zero image offsets, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted JPEG2000 data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7012 |
909 | FFmpeg | 3819db745da2ac7fb3faacb116788c32f4753f34 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/3819db745da2ac7fb3faacb116788c32f4753f34 | avcodec/rpza: Perform pointer advance and checks before using the pointers
Fixes out of array accesses
Fixes Ticket2850
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | static void rpza_decode_stream(RpzaContext *s)
{
int width = s->avctx->width;
int stride = s->frame.linesize[0] / 2;
int row_inc = stride - 4;
int stream_ptr = 0;
int chunk_size;
unsigned char opcode;
int n_blocks;
unsigned short colorA = 0, colorB;
unsigned short color4[4];
unsi... | 269,902,084,834,802,800,000,000,000,000,000,000,000 | rpza.c | 178,523,187,513,410,220,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7009 | The rpza_decode_stream function in libavcodec/rpza.c in FFmpeg before 2.1 does not properly maintain a pointer to pixel data, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Apple RPZA data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7009 |
158,737 | FFmpeg | 3819db745da2ac7fb3faacb116788c32f4753f34 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/3819db745da2ac7fb3faacb116788c32f4753f34 | avcodec/rpza: Perform pointer advance and checks before using the pointers
Fixes out of array accesses
Fixes Ticket2850
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | static void rpza_decode_stream(RpzaContext *s)
{
int width = s->avctx->width;
int stride = s->frame.linesize[0] / 2;
int row_inc = stride - 4;
int stream_ptr = 0;
int chunk_size;
unsigned char opcode;
int n_blocks;
unsigned short colorA = 0, colorB;
unsigned short color4[4];
unsi... | 199,142,065,752,138,400,000,000,000,000,000,000,000 | rpza.c | 145,110,260,770,130,120,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-7009 | The rpza_decode_stream function in libavcodec/rpza.c in FFmpeg before 2.1 does not properly maintain a pointer to pixel data, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Apple RPZA data. | https://nvd.nist.gov/vuln/detail/CVE-2013-7009 |
910 | krb5 | c2ccf4197f697c4ff143b8a786acdd875e70a89d | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/c2ccf4197f697c4ff143b8a786acdd875e70a89d | Multi-realm KDC null deref [CVE-2013-1418]
If a KDC serves multiple realms, certain requests can cause
setup_server_realm() to dereference a null pointer, crashing the KDC.
CVSSv2: AV:N/AC:M/Au:N/C:N/I:N/A:P/E:POC/RL:OF/RC:C
A related but more minor vulnerability requires authentication to
exploit, and is only prese... | 1 | setup_server_realm(krb5_principal sprinc)
{
krb5_error_code kret;
kdc_realm_t *newrealm;
kret = 0;
if (kdc_numrealms > 1) {
if (!(newrealm = find_realm_data(sprinc->realm.data,
(krb5_ui_4) sprinc->realm.length)))
kret = ENOE... | 321,135,329,376,345,060,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2013-1418 | The setup_server_realm function in main.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.7, when multiple realms are configured, allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted request. | https://nvd.nist.gov/vuln/detail/CVE-2013-1418 |
158,739 | krb5 | c2ccf4197f697c4ff143b8a786acdd875e70a89d | https://github.com/krb5/krb5 | https://github.com/krb5/krb5/commit/c2ccf4197f697c4ff143b8a786acdd875e70a89d | Multi-realm KDC null deref [CVE-2013-1418]
If a KDC serves multiple realms, certain requests can cause
setup_server_realm() to dereference a null pointer, crashing the KDC.
CVSSv2: AV:N/AC:M/Au:N/C:N/I:N/A:P/E:POC/RL:OF/RC:C
A related but more minor vulnerability requires authentication to
exploit, and is only prese... | 0 | setup_server_realm(krb5_principal sprinc)
{
krb5_error_code kret;
kdc_realm_t *newrealm;
kret = 0;
if (sprinc == NULL)
return NULL;
if (kdc_numrealms > 1) {
if (!(newrealm = find_realm_data(sprinc->realm.data,
(krb5_ui_4) s... | 167,829,479,696,001,630,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2013-1418 | The setup_server_realm function in main.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.10.7, when multiple realms are configured, allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via a crafted request. | https://nvd.nist.gov/vuln/detail/CVE-2013-1418 |
911 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 1 | static int uio_mmap_physical(struct vm_area_struct *vma)
{
struct uio_device *idev = vma->vm_private_data;
int mi = uio_find_mem_index(vma);
if (mi < 0)
return -EINVAL;
vma->vm_ops = &uio_physical_vm_ops;
vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
return remap_pfn_range(vma,
... | 124,769,329,517,591,230,000,000,000,000,000,000,000 | uio.c | 189,572,155,418,257,000,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
158,740 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 0 | static int uio_mmap_physical(struct vm_area_struct *vma)
{
struct uio_device *idev = vma->vm_private_data;
int mi = uio_find_mem_index(vma);
struct uio_mem *mem;
if (mi < 0)
return -EINVAL;
mem = idev->info->mem + mi;
if (vma->vm_end - vma->vm_start > mem->size)
return -EINVAL;
vma->vm_ops = &uio_ph... | 37,065,271,855,217,370,000,000,000,000,000,000,000 | uio.c | 36,047,993,049,944,990,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
912 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 1 | int au1100fb_fb_mmap(struct fb_info *fbi, struct vm_area_struct *vma)
{
struct au1100fb_device *fbdev;
unsigned int len;
unsigned long start=0, off;
fbdev = to_au1100fb_device(fbi);
if (vma->vm_pgoff > (~0UL >> PAGE_SHIFT)) {
return -EINVAL;
}
start = fbdev->fb_phys & PAGE_MASK;
len = PAGE_ALIGN((star... | 177,273,139,877,749,560,000,000,000,000,000,000,000 | au1100fb.c | 171,201,343,492,238,250,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
158,741 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 0 | int au1100fb_fb_mmap(struct fb_info *fbi, struct vm_area_struct *vma)
{
struct au1100fb_device *fbdev;
fbdev = to_au1100fb_device(fbi);
vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
pgprot_val(vma->vm_page_prot) |= (6 << 9); //CCA=6
return vm_iomap_memory(vma, fbdev->fb_phys, fbdev->fb_len);... | 1,623,279,895,322,387,800,000,000,000,000,000,000 | au1100fb.c | 77,902,258,379,140,110,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
913 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 1 | static int au1200fb_fb_mmap(struct fb_info *info, struct vm_area_struct *vma)
{
unsigned int len;
unsigned long start=0, off;
struct au1200fb_device *fbdev = info->par;
if (vma->vm_pgoff > (~0UL >> PAGE_SHIFT)) {
return -EINVAL;
}
start = fbdev->fb_phys & PAGE_MASK;
len = PAGE_ALIGN((start & ~PAGE_MASK) +... | 67,752,722,467,221,080,000,000,000,000,000,000,000 | au1200fb.c | 20,588,446,351,461,834,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
158,742 | linux | 7314e613d5ff9f0934f7a0f74ed7973b903315d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7314e613d5ff9f0934f7a0f74ed7973b903315d1 | Fix a few incorrectly checked [io_]remap_pfn_range() calls
Nico Golde reports a few straggling uses of [io_]remap_pfn_range() that
really should use the vm_iomap_memory() helper. This trivially converts
two of them to the helper, and comments about why the third one really
needs to continue to use remap_pfn_range(), ... | 0 | static int au1200fb_fb_mmap(struct fb_info *info, struct vm_area_struct *vma)
{
struct au1200fb_device *fbdev = info->par;
vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
pgprot_val(vma->vm_page_prot) |= _CACHE_MASK; /* CCA=7 */
return vm_iomap_memory(vma, fbdev->fb_phys, fbdev->fb_len);
}
| 258,558,073,391,048,840,000,000,000,000,000,000,000 | au1200fb.c | 40,760,652,179,933,860,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6763 | The uio_mmap_physical function in drivers/uio/uio.c in the Linux kernel before 3.12 does not validate the size of a memory block, which allows local users to cause a denial of service (memory corruption) or possibly gain privileges via crafted mmap operations, a different vulnerability than CVE-2013-4511. | https://nvd.nist.gov/vuln/detail/CVE-2013-6763 |
914 | linux | cf970c002d270c36202bd5b9c2804d3097a52da0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cf970c002d270c36202bd5b9c2804d3097a52da0 | ping: prevent NULL pointer dereference on write to msg_name
A plain read() on a socket does set msg->msg_name to NULL. So check for
NULL pointer first.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net> | 1 | int ping_recvmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
size_t len, int noblock, int flags, int *addr_len)
{
struct inet_sock *isk = inet_sk(sk);
int family = sk->sk_family;
struct sk_buff *skb;
int copied, err;
pr_debug("ping_recvmsg(sk=%p,sk->num=%u)\n", isk, isk->inet_num);
err = -EOPNOT... | 155,904,653,362,942,950,000,000,000,000,000,000,000 | ping.c | 52,362,142,179,938,880,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-6432 | The ping_recvmsg function in net/ipv4/ping.c in the Linux kernel before 3.12.4 does not properly interact with read system calls on ping sockets, which allows local users to cause a denial of service (NULL pointer dereference and system crash) by leveraging unspecified privileges to execute a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-6432 |
158,743 | linux | cf970c002d270c36202bd5b9c2804d3097a52da0 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/cf970c002d270c36202bd5b9c2804d3097a52da0 | ping: prevent NULL pointer dereference on write to msg_name
A plain read() on a socket does set msg->msg_name to NULL. So check for
NULL pointer first.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net> | 0 | int ping_recvmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
size_t len, int noblock, int flags, int *addr_len)
{
struct inet_sock *isk = inet_sk(sk);
int family = sk->sk_family;
struct sk_buff *skb;
int copied, err;
pr_debug("ping_recvmsg(sk=%p,sk->num=%u)\n", isk, isk->inet_num);
err = -EOPNOT... | 170,118,124,667,852,840,000,000,000,000,000,000,000 | ping.c | 208,150,909,002,443,060,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-6432 | The ping_recvmsg function in net/ipv4/ping.c in the Linux kernel before 3.12.4 does not properly interact with read system calls on ping sockets, which allows local users to cause a denial of service (NULL pointer dereference and system crash) by leveraging unspecified privileges to execute a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-6432 |
915 | linux | f856567b930dfcdbc3323261bf77240ccdde01f5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f856567b930dfcdbc3323261bf77240ccdde01f5 | aacraid: missing capable() check in compat ioctl
In commit d496f94d22d1 ('[SCSI] aacraid: fix security weakness') we
added a check on CAP_SYS_RAWIO to the ioctl. The compat ioctls need the
check as well.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torv... | 1 | static int aac_compat_ioctl(struct scsi_device *sdev, int cmd, void __user *arg)
{
struct aac_dev *dev = (struct aac_dev *)sdev->host->hostdata;
return aac_compat_do_ioctl(dev, cmd, (unsigned long)arg);
}
| 240,252,914,944,451,600,000,000,000,000,000,000,000 | linit.c | 335,956,036,663,395,150,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-6383 | The aac_compat_ioctl function in drivers/scsi/aacraid/linit.c in the Linux kernel before 3.11.8 does not require the CAP_SYS_RAWIO capability, which allows local users to bypass intended access restrictions via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-6383 |
158,744 | linux | f856567b930dfcdbc3323261bf77240ccdde01f5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/f856567b930dfcdbc3323261bf77240ccdde01f5 | aacraid: missing capable() check in compat ioctl
In commit d496f94d22d1 ('[SCSI] aacraid: fix security weakness') we
added a check on CAP_SYS_RAWIO to the ioctl. The compat ioctls need the
check as well.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <torv... | 0 | static int aac_compat_ioctl(struct scsi_device *sdev, int cmd, void __user *arg)
{
struct aac_dev *dev = (struct aac_dev *)sdev->host->hostdata;
if (!capable(CAP_SYS_RAWIO))
return -EPERM;
return aac_compat_do_ioctl(dev, cmd, (unsigned long)arg);
}
| 266,596,673,331,677,600,000,000,000,000,000,000,000 | linit.c | 174,196,362,056,113,520,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-6383 | The aac_compat_ioctl function in drivers/scsi/aacraid/linit.c in the Linux kernel before 3.11.8 does not require the CAP_SYS_RAWIO capability, which allows local users to bypass intended access restrictions via a crafted ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-6383 |
916 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 1 | int qeth_snmp_command(struct qeth_card *card, char __user *udata)
{
struct qeth_cmd_buffer *iob;
struct qeth_ipa_cmd *cmd;
struct qeth_snmp_ureq *ureq;
int req_len;
struct qeth_arp_query_info qinfo = {0, };
int rc = 0;
QETH_CARD_TEXT(card, 3, "snmpcmd");
if (card->info.guestlan)
return -EOPNOTSUPP;
... | 104,798,081,715,700,400,000,000,000,000,000,000,000 | qeth_core_main.c | 236,635,939,498,951,130,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
158,745 | linux | 6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6fb392b1a63ae36c31f62bc3fc8630b49d602b62 | qeth: avoid buffer overflow in snmp ioctl
Check user-defined length in snmp ioctl request and allow request
only if it fits into a qeth command buffer.
Signed-off-by: Ursula Braun <ursula.braun@de.ibm.com>
Signed-off-by: Frank Blaschka <frank.blaschka@de.ibm.com>
Reviewed-by: Heiko Carstens <heicars2@linux.vnet.ibm.c... | 0 | int qeth_snmp_command(struct qeth_card *card, char __user *udata)
{
struct qeth_cmd_buffer *iob;
struct qeth_ipa_cmd *cmd;
struct qeth_snmp_ureq *ureq;
unsigned int req_len;
struct qeth_arp_query_info qinfo = {0, };
int rc = 0;
QETH_CARD_TEXT(card, 3, "snmpcmd");
if (card->info.guestlan)
return -EOPNO... | 169,202,937,829,379,530,000,000,000,000,000,000,000 | qeth_core_main.c | 172,045,772,512,734,900,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-6381 | Buffer overflow in the qeth_snmp_command function in drivers/s390/net/qeth_core_main.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service or possibly have unspecified other impact via an SNMP ioctl call with a length value that is incompatible with the command-buffer size. | https://nvd.nist.gov/vuln/detail/CVE-2013-6381 |
917 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 1 | static ssize_t lbs_debugfs_write(struct file *f, const char __user *buf,
size_t cnt, loff_t *ppos)
{
int r, i;
char *pdata;
char *p;
char *p0;
char *p1;
char *p2;
struct debug_data *d = f->private_data;
pdata = kmalloc(cnt, GFP_KERNEL);
if (pdata == NULL)
return 0;
if (copy_from_user(pdata, b... | 75,946,839,779,695,430,000,000,000,000,000,000,000 | debugfs.c | 106,884,417,614,616,100,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
158,747 | linux | a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a497e47d4aec37aaf8f13509f3ef3d1f6a717d88 | libertas: potential oops in debugfs
If we do a zero size allocation then it will oops. Also we can't be
sure the user passes us a NUL terminated string so I've added a
terminator.
This code can only be triggered by root.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-... | 0 | static ssize_t lbs_debugfs_write(struct file *f, const char __user *buf,
size_t cnt, loff_t *ppos)
{
int r, i;
char *pdata;
char *p;
char *p0;
char *p1;
char *p2;
struct debug_data *d = f->private_data;
if (cnt == 0)
return 0;
pdata = kmalloc(cnt + 1, GFP_KERNEL);
if (pdata == NULL)
return 0... | 233,211,545,593,580,200,000,000,000,000,000,000,000 | debugfs.c | 41,257,289,586,596,890,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6378 | The lbs_debugfs_write function in drivers/net/wireless/libertas/debugfs.c in the Linux kernel through 3.12.1 allows local users to cause a denial of service (OOPS) by leveraging root privileges for a zero-length write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-6378 |
918 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 1 | static void recalculate_apic_map(struct kvm *kvm)
{
struct kvm_apic_map *new, *old = NULL;
struct kvm_vcpu *vcpu;
int i;
new = kzalloc(sizeof(struct kvm_apic_map), GFP_KERNEL);
mutex_lock(&kvm->arch.apic_map_lock);
if (!new)
goto out;
new->ldr_bits = 8;
/* flat mode is default */
new->cid_shift = 8;
... | 90,650,423,270,339,170,000,000,000,000,000,000,000 | lapic.c | 190,243,646,842,195,860,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
158,748 | linux | 17d68b763f09a9ce824ae23eb62c9efc57b69271 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/17d68b763f09a9ce824ae23eb62c9efc57b69271 | KVM: x86: fix guest-initiated crash with x2apic (CVE-2013-6376)
A guest can cause a BUG_ON() leading to a host kernel crash.
When the guest writes to the ICR to request an IPI, while in x2apic
mode the following things happen, the destination is read from
ICR2, which is a register that the guest can control.
kvm_irq_... | 0 | static void recalculate_apic_map(struct kvm *kvm)
{
struct kvm_apic_map *new, *old = NULL;
struct kvm_vcpu *vcpu;
int i;
new = kzalloc(sizeof(struct kvm_apic_map), GFP_KERNEL);
mutex_lock(&kvm->arch.apic_map_lock);
if (!new)
goto out;
new->ldr_bits = 8;
/* flat mode is default */
new->cid_shift = 8;
... | 255,330,493,411,169,600,000,000,000,000,000,000,000 | lapic.c | 117,888,982,784,563,870,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-6376 | The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM subsystem in the Linux kernel through 3.12.5 allows guest OS users to cause a denial of service (host OS crash) via a crafted ICR write operation in x2apic mode. | https://nvd.nist.gov/vuln/detail/CVE-2013-6376 |
929 | polarssl | 1922a4e6aade7b1d685af19d4d9339ddb5c02859 | https://github.com/polarssl/polarssl | https://github.com/polarssl/polarssl/commit/1922a4e6aade7b1d685af19d4d9339ddb5c02859 | ssl_parse_certificate() now calls x509parse_crt_der() directly | 1 | int ssl_parse_certificate( ssl_context *ssl )
{
int ret;
size_t i, n;
SSL_DEBUG_MSG( 2, ( "=> parse certificate" ) );
if( ssl->endpoint == SSL_IS_SERVER &&
ssl->authmode == SSL_VERIFY_NONE )
{
ssl->verify_result = BADCERT_SKIP_VERIFY;
SSL_DEBUG_MSG( 2, ( "<= skip parse cert... | 79,433,638,809,905,910,000,000,000,000,000,000,000 | ssl_tls.c | 193,081,241,478,287,840,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4623 | The x509parse_crt function in x509.h in PolarSSL 1.1.x before 1.1.7 and 1.2.x before 1.2.8 does not properly parse certificate messages during the SSL/TLS handshake, which allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a certificate message that contains a PEM encoded certi... | https://nvd.nist.gov/vuln/detail/CVE-2013-4623 |
158,755 | polarssl | 1922a4e6aade7b1d685af19d4d9339ddb5c02859 | https://github.com/polarssl/polarssl | https://github.com/polarssl/polarssl/commit/1922a4e6aade7b1d685af19d4d9339ddb5c02859 | ssl_parse_certificate() now calls x509parse_crt_der() directly | 0 | int ssl_parse_certificate( ssl_context *ssl )
{
int ret;
size_t i, n;
SSL_DEBUG_MSG( 2, ( "=> parse certificate" ) );
if( ssl->endpoint == SSL_IS_SERVER &&
ssl->authmode == SSL_VERIFY_NONE )
{
ssl->verify_result = BADCERT_SKIP_VERIFY;
SSL_DEBUG_MSG( 2, ( "<= skip parse cert... | 246,481,471,940,867,240,000,000,000,000,000,000,000 | ssl_tls.c | 176,090,796,145,832,660,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4623 | The x509parse_crt function in x509.h in PolarSSL 1.1.x before 1.1.7 and 1.2.x before 1.2.8 does not properly parse certificate messages during the SSL/TLS handshake, which allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a certificate message that contains a PEM encoded certi... | https://nvd.nist.gov/vuln/detail/CVE-2013-4623 |
931 | linux | 04bcef2a83f40c6db24222b27a52892cba39dffb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/04bcef2a83f40c6db24222b27a52892cba39dffb | ipvs: Add boundary check on ioctl arguments
The ipvs code has a nifty system for doing the size of ioctl command
copies; it defines an array with values into which it indexes the cmd
to find the right length.
Unfortunately, the ipvs code forgot to check if the cmd was in the
range that the array provides, allowing fo... | 1 | do_ip_vs_set_ctl(struct sock *sk, int cmd, void __user *user, unsigned int len)
{
int ret;
unsigned char arg[MAX_ARG_LEN];
struct ip_vs_service_user *usvc_compat;
struct ip_vs_service_user_kern usvc;
struct ip_vs_service *svc;
struct ip_vs_dest_user *udest_compat;
struct ip_vs_dest_user_kern udest;
if (!capab... | 83,673,314,409,807,090,000,000,000,000,000,000,000 | ip_vs_ctl.c | 16,053,961,743,391,224,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4588 | Multiple stack-based buffer overflows in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 2.6.33, when CONFIG_IP_VS is used, allow local users to gain privileges by leveraging the CAP_NET_ADMIN capability for (1) a getsockopt system call, related to the do_ip_vs_get_ctl function, or (2) a setsockopt system cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-4588 |
158,756 | linux | 04bcef2a83f40c6db24222b27a52892cba39dffb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/04bcef2a83f40c6db24222b27a52892cba39dffb | ipvs: Add boundary check on ioctl arguments
The ipvs code has a nifty system for doing the size of ioctl command
copies; it defines an array with values into which it indexes the cmd
to find the right length.
Unfortunately, the ipvs code forgot to check if the cmd was in the
range that the array provides, allowing fo... | 0 | do_ip_vs_set_ctl(struct sock *sk, int cmd, void __user *user, unsigned int len)
{
int ret;
unsigned char arg[MAX_ARG_LEN];
struct ip_vs_service_user *usvc_compat;
struct ip_vs_service_user_kern usvc;
struct ip_vs_service *svc;
struct ip_vs_dest_user *udest_compat;
struct ip_vs_dest_user_kern udest;
if (!capab... | 157,614,413,276,462,150,000,000,000,000,000,000,000 | ip_vs_ctl.c | 105,962,925,241,335,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4588 | Multiple stack-based buffer overflows in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 2.6.33, when CONFIG_IP_VS is used, allow local users to gain privileges by leveraging the CAP_NET_ADMIN capability for (1) a getsockopt system call, related to the do_ip_vs_get_ctl function, or (2) a setsockopt system cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-4588 |
9,228 | linux | 04bcef2a83f40c6db24222b27a52892cba39dffb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/04bcef2a83f40c6db24222b27a52892cba39dffb | ipvs: Add boundary check on ioctl arguments
The ipvs code has a nifty system for doing the size of ioctl command
copies; it defines an array with values into which it indexes the cmd
to find the right length.
Unfortunately, the ipvs code forgot to check if the cmd was in the
range that the array provides, allowing fo... | 1 | do_ip_vs_get_ctl(struct sock *sk, int cmd, void __user *user, int *len)
{
unsigned char arg[128];
int ret = 0;
if (!capable(CAP_NET_ADMIN))
return -EPERM;
if (*len < get_arglen[GET_CMDID(cmd)]) {
pr_err("get_ctl: len %u < %u\n",
*len, get_arglen[GET_CMDID(cmd)]);
return -EINVAL;
}
i... | 171,209,038,462,118,170,000,000,000,000,000,000,000 | ip_vs_ctl.c | 16,053,961,743,391,224,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4588 | Multiple stack-based buffer overflows in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 2.6.33, when CONFIG_IP_VS is used, allow local users to gain privileges by leveraging the CAP_NET_ADMIN capability for (1) a getsockopt system call, related to the do_ip_vs_get_ctl function, or (2) a setsockopt system cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-4588 |
184,379 | linux | 04bcef2a83f40c6db24222b27a52892cba39dffb | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/04bcef2a83f40c6db24222b27a52892cba39dffb | ipvs: Add boundary check on ioctl arguments
The ipvs code has a nifty system for doing the size of ioctl command
copies; it defines an array with values into which it indexes the cmd
to find the right length.
Unfortunately, the ipvs code forgot to check if the cmd was in the
range that the array provides, allowing fo... | 0 | do_ip_vs_get_ctl(struct sock *sk, int cmd, void __user *user, int *len)
{
unsigned char arg[128];
int ret = 0;
unsigned int copylen;
if (!capable(CAP_NET_ADMIN))
return -EPERM;
if (cmd < IP_VS_BASE_CTL || cmd > IP_VS_SO_GET_MAX)
return -EINVAL;
if (*len < get_arglen[GET_CMDID(cmd)]) {
pr_err("ge... | 17,115,367,795,766,587,000,000,000,000,000,000,000 | ip_vs_ctl.c | 105,962,925,241,335,800,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4588 | Multiple stack-based buffer overflows in net/netfilter/ipvs/ip_vs_ctl.c in the Linux kernel before 2.6.33, when CONFIG_IP_VS is used, allow local users to gain privileges by leveraging the CAP_NET_ADMIN capability for (1) a getsockopt system call, related to the do_ip_vs_get_ctl function, or (2) a setsockopt system cal... | https://nvd.nist.gov/vuln/detail/CVE-2013-4588 |
932 | linux | 338c7dbadd2671189cec7faf64c84d01071b3f96 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/338c7dbadd2671189cec7faf64c84d01071b3f96 | KVM: Improve create VCPU parameter (CVE-2013-4587)
In multiple functions the vcpu_id is used as an offset into a bitfield. Ag
malicious user could specify a vcpu_id greater than 255 in order to set or
clear bits in kernel memory. This could be used to elevate priveges in the
kernel. This patch verifies that the vcp... | 1 | static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)
{
int r;
struct kvm_vcpu *vcpu, *v;
vcpu = kvm_arch_vcpu_create(kvm, id);
if (IS_ERR(vcpu))
return PTR_ERR(vcpu);
preempt_notifier_init(&vcpu->preempt_notifier, &kvm_preempt_ops);
r = kvm_arch_vcpu_setup(vcpu);
if (r)
goto vcpu_destroy;
... | 78,071,846,559,468,940,000,000,000,000,000,000,000 | kvm_main.c | 162,946,847,399,016,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4587 | Array index error in the kvm_vm_ioctl_create_vcpu function in virt/kvm/kvm_main.c in the KVM subsystem in the Linux kernel through 3.12.5 allows local users to gain privileges via a large id value. | https://nvd.nist.gov/vuln/detail/CVE-2013-4587 |
158,757 | linux | 338c7dbadd2671189cec7faf64c84d01071b3f96 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/338c7dbadd2671189cec7faf64c84d01071b3f96 | KVM: Improve create VCPU parameter (CVE-2013-4587)
In multiple functions the vcpu_id is used as an offset into a bitfield. Ag
malicious user could specify a vcpu_id greater than 255 in order to set or
clear bits in kernel memory. This could be used to elevate priveges in the
kernel. This patch verifies that the vcp... | 0 | static int kvm_vm_ioctl_create_vcpu(struct kvm *kvm, u32 id)
{
int r;
struct kvm_vcpu *vcpu, *v;
if (id >= KVM_MAX_VCPUS)
return -EINVAL;
vcpu = kvm_arch_vcpu_create(kvm, id);
if (IS_ERR(vcpu))
return PTR_ERR(vcpu);
preempt_notifier_init(&vcpu->preempt_notifier, &kvm_preempt_ops);
r = kvm_arch_vcpu... | 16,194,852,578,092,710,000,000,000,000,000,000,000 | kvm_main.c | 79,123,672,423,445,420,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4587 | Array index error in the kvm_vm_ioctl_create_vcpu function in virt/kvm/kvm_main.c in the KVM subsystem in the Linux kernel through 3.12.5 allows local users to gain privileges via a large id value. | https://nvd.nist.gov/vuln/detail/CVE-2013-4587 |
933 | linux | 0e033e04c2678dbbe74a46b23fffb7bb918c288e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e033e04c2678dbbe74a46b23fffb7bb918c288e | ipv6: fix headroom calculation in udp6_ufo_fragment
Commit 1e2bd517c108816220f262d7954b697af03b5f9c ("udp6: Fix udp
fragmentation for tunnel traffic.") changed the calculation if
there is enough space to include a fragment header in the skb from a
skb->mac_header dervived one to skb_headroom. Because we already peeled... | 1 | static struct sk_buff *udp6_ufo_fragment(struct sk_buff *skb,
netdev_features_t features)
{
struct sk_buff *segs = ERR_PTR(-EINVAL);
unsigned int mss;
unsigned int unfrag_ip6hlen, unfrag_len;
struct frag_hdr *fptr;
u8 *packet_start, *prevhdr;
u8 nexthdr;
u8 frag_hdr_sz = sizeof(struct frag_hdr);
int offse... | 168,959,719,558,504,360,000,000,000,000,000,000,000 | udp_offload.c | 333,651,348,407,875,630,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4563 | The udp6_ufo_fragment function in net/ipv6/udp_offload.c in the Linux kernel through 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly perform a certain size comparison before inserting a fragment header, which allows remote attackers to cause a denial of service (panic) via a large IPv6 UDP pack... | https://nvd.nist.gov/vuln/detail/CVE-2013-4563 |
158,758 | linux | 0e033e04c2678dbbe74a46b23fffb7bb918c288e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/0e033e04c2678dbbe74a46b23fffb7bb918c288e | ipv6: fix headroom calculation in udp6_ufo_fragment
Commit 1e2bd517c108816220f262d7954b697af03b5f9c ("udp6: Fix udp
fragmentation for tunnel traffic.") changed the calculation if
there is enough space to include a fragment header in the skb from a
skb->mac_header dervived one to skb_headroom. Because we already peeled... | 0 | static struct sk_buff *udp6_ufo_fragment(struct sk_buff *skb,
netdev_features_t features)
{
struct sk_buff *segs = ERR_PTR(-EINVAL);
unsigned int mss;
unsigned int unfrag_ip6hlen, unfrag_len;
struct frag_hdr *fptr;
u8 *packet_start, *prevhdr;
u8 nexthdr;
u8 frag_hdr_sz = sizeof(struct frag_hdr);
int offse... | 153,608,604,574,028,520,000,000,000,000,000,000,000 | udp_offload.c | 211,155,262,577,847,330,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4563 | The udp6_ufo_fragment function in net/ipv6/udp_offload.c in the Linux kernel through 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly perform a certain size comparison before inserting a fragment header, which allows remote attackers to cause a denial of service (panic) via a large IPv6 UDP pack... | https://nvd.nist.gov/vuln/detail/CVE-2013-4563 |
934 | linux | a8b33654b1e3b0c74d4a1fed041c9aae50b3c427 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a8b33654b1e3b0c74d4a1fed041c9aae50b3c427 | Staging: sb105x: info leak in mp_get_count()
The icount.reserved[] array isn't initialized so it leaks stack
information to userspace.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Li... | 1 | static int mp_get_count(struct sb_uart_state *state, struct serial_icounter_struct *icnt)
{
struct serial_icounter_struct icount;
struct sb_uart_icount cnow;
struct sb_uart_port *port = state->port;
spin_lock_irq(&port->lock);
memcpy(&cnow, &port->icount, sizeof(struct sb_uart_icount));
spin_unlock_irq(&por... | 46,385,543,661,315,150,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2013-4516 | The mp_get_count function in drivers/staging/sb105x/sb_pci_mp.c in the Linux kernel before 3.12 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory via a TIOCGICOUNT ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4516 |
158,759 | linux | a8b33654b1e3b0c74d4a1fed041c9aae50b3c427 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a8b33654b1e3b0c74d4a1fed041c9aae50b3c427 | Staging: sb105x: info leak in mp_get_count()
The icount.reserved[] array isn't initialized so it leaks stack
information to userspace.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Li... | 0 | static int mp_get_count(struct sb_uart_state *state, struct serial_icounter_struct *icnt)
{
struct serial_icounter_struct icount = {};
struct sb_uart_icount cnow;
struct sb_uart_port *port = state->port;
spin_lock_irq(&port->lock);
memcpy(&cnow, &port->icount, sizeof(struct sb_uart_icount));
spin_unlock_irq... | 324,019,436,882,545,070,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2013-4516 | The mp_get_count function in drivers/staging/sb105x/sb_pci_mp.c in the Linux kernel before 3.12 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel stack memory via a TIOCGICOUNT ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4516 |
935 | linux | 8d1e72250c847fa96498ec029891de4dc638a5ba | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8d1e72250c847fa96498ec029891de4dc638a5ba | Staging: bcm: info leak in ioctl
The DevInfo.u32Reserved[] array isn't initialized so it leaks kernel
information to user space.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus To... | 1 | static long bcm_char_ioctl(struct file *filp, UINT cmd, ULONG arg)
{
struct bcm_tarang_data *pTarang = filp->private_data;
void __user *argp = (void __user *)arg;
struct bcm_mini_adapter *Adapter = pTarang->Adapter;
INT Status = STATUS_FAILURE;
int timeout = 0;
struct bcm_ioctl_buffer IoBuffer;
int bytes;
BCM_... | 15,758,140,552,209,270,000,000,000,000,000,000,000 | Bcmchar.c | 297,513,847,153,823,100,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-4515 | The bcm_char_ioctl function in drivers/staging/bcm/Bcmchar.c in the Linux kernel before 3.12 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via an IOCTL_BCM_GET_DEVICE_DRIVER_INFO ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4515 |
158,760 | linux | 8d1e72250c847fa96498ec029891de4dc638a5ba | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8d1e72250c847fa96498ec029891de4dc638a5ba | Staging: bcm: info leak in ioctl
The DevInfo.u32Reserved[] array isn't initialized so it leaks kernel
information to user space.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus To... | 0 | static long bcm_char_ioctl(struct file *filp, UINT cmd, ULONG arg)
{
struct bcm_tarang_data *pTarang = filp->private_data;
void __user *argp = (void __user *)arg;
struct bcm_mini_adapter *Adapter = pTarang->Adapter;
INT Status = STATUS_FAILURE;
int timeout = 0;
struct bcm_ioctl_buffer IoBuffer;
int bytes;
BCM_... | 175,369,601,537,047,660,000,000,000,000,000,000,000 | Bcmchar.c | 323,504,708,855,947,280,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2013-4515 | The bcm_char_ioctl function in drivers/staging/bcm/Bcmchar.c in the Linux kernel before 3.12 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory via an IOCTL_BCM_GET_DEVICE_DRIVER_INFO ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2013-4515 |
936 | linux | b5e2f339865fb443107e5b10603e53bbc92dc054 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5e2f339865fb443107e5b10603e53bbc92dc054 | staging: wlags49_h2: buffer overflow setting station name
We need to check the length parameter before doing the memcpy(). I've
actually changed it to strlcpy() as well so that it's NUL terminated.
You need CAP_NET_ADMIN to trigger these so it's not the end of the
world.
Reported-by: Nico Golde <nico@ngolde.de>
Rep... | 1 | int wvlan_set_station_nickname(struct net_device *dev,
struct iw_request_info *info,
union iwreq_data *wrqu,
char *extra)
{
struct wl_private *lp = wl_priv(dev);
unsigned long flags;
int ret = 0;
/*------------------------------------------------------------------------*/
DB... | 62,431,484,736,668,090,000,000,000,000,000,000,000 | wl_priv.c | 140,308,459,115,906,430,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4514 | Multiple buffer overflows in drivers/staging/wlags49_h2/wl_priv.c in the Linux kernel before 3.12 allow local users to cause a denial of service or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability and providing a long station-name string, related to the (1) wvlan_uil_put_info and (2) wv... | https://nvd.nist.gov/vuln/detail/CVE-2013-4514 |
31,176 | linux | b5e2f339865fb443107e5b10603e53bbc92dc054 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5e2f339865fb443107e5b10603e53bbc92dc054 | staging: wlags49_h2: buffer overflow setting station name
We need to check the length parameter before doing the memcpy(). I've
actually changed it to strlcpy() as well so that it's NUL terminated.
You need CAP_NET_ADMIN to trigger these so it's not the end of the
world.
Reported-by: Nico Golde <nico@ngolde.de>
Rep... | 0 | int wvlan_set_netname(struct net_device *dev,
struct iw_request_info *info,
union iwreq_data *wrqu,
char *extra)
{
struct wl_private *lp = wl_priv(dev);
unsigned long flags;
int ret = 0;
/*------------------------------------------------------------------------*/
DBG_FUNC("wvlan_set_netna... | 162,205,244,003,191,240,000,000,000,000,000,000,000 | wl_priv.c | 60,757,582,669,243,510,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4514 | Multiple buffer overflows in drivers/staging/wlags49_h2/wl_priv.c in the Linux kernel before 3.12 allow local users to cause a denial of service or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability and providing a long station-name string, related to the (1) wvlan_uil_put_info and (2) wv... | https://nvd.nist.gov/vuln/detail/CVE-2013-4514 |
937 | linux | b5e2f339865fb443107e5b10603e53bbc92dc054 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5e2f339865fb443107e5b10603e53bbc92dc054 | staging: wlags49_h2: buffer overflow setting station name
We need to check the length parameter before doing the memcpy(). I've
actually changed it to strlcpy() as well so that it's NUL terminated.
You need CAP_NET_ADMIN to trigger these so it's not the end of the
world.
Reported-by: Nico Golde <nico@ngolde.de>
Rep... | 1 | int wvlan_uil_put_info(struct uilreq *urq, struct wl_private *lp)
{
int result = 0;
ltv_t *pLtv;
bool_t ltvAllocated = FALSE;
ENCSTRCT sEncryption;
#ifdef USE_WDS
hcf_16 hcfPort = HCF_PORT_0;
#endif /* USE_WDS */
/*---... | 192,300,055,996,805,040,000,000,000,000,000,000,000 | wl_priv.c | 140,308,459,115,906,430,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4514 | Multiple buffer overflows in drivers/staging/wlags49_h2/wl_priv.c in the Linux kernel before 3.12 allow local users to cause a denial of service or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability and providing a long station-name string, related to the (1) wvlan_uil_put_info and (2) wv... | https://nvd.nist.gov/vuln/detail/CVE-2013-4514 |
158,762 | linux | b5e2f339865fb443107e5b10603e53bbc92dc054 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b5e2f339865fb443107e5b10603e53bbc92dc054 | staging: wlags49_h2: buffer overflow setting station name
We need to check the length parameter before doing the memcpy(). I've
actually changed it to strlcpy() as well so that it's NUL terminated.
You need CAP_NET_ADMIN to trigger these so it's not the end of the
world.
Reported-by: Nico Golde <nico@ngolde.de>
Rep... | 0 | int wvlan_uil_put_info(struct uilreq *urq, struct wl_private *lp)
{
int result = 0;
ltv_t *pLtv;
bool_t ltvAllocated = FALSE;
ENCSTRCT sEncryption;
size_t len;
#ifdef USE_WDS
hcf_16 hcfPort = HCF_PORT_0;
#endif /* US... | 43,124,070,682,619,750,000,000,000,000,000,000,000 | wl_priv.c | 60,757,582,669,243,510,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4514 | Multiple buffer overflows in drivers/staging/wlags49_h2/wl_priv.c in the Linux kernel before 3.12 allow local users to cause a denial of service or possibly have unspecified other impact by leveraging the CAP_NET_ADMIN capability and providing a long station-name string, related to the (1) wvlan_uil_put_info and (2) wv... | https://nvd.nist.gov/vuln/detail/CVE-2013-4514 |
938 | linux | c2c65cd2e14ada6de44cb527e7f1990bede24e15 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c2c65cd2e14ada6de44cb527e7f1990bede24e15 | staging: ozwpan: prevent overflow in oz_cdev_write()
We need to check "count" so we don't overflow the ei->data buffer.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <t... | 1 | static ssize_t oz_cdev_write(struct file *filp, const char __user *buf,
size_t count, loff_t *fpos)
{
struct oz_pd *pd;
struct oz_elt_buf *eb;
struct oz_elt_info *ei;
struct oz_elt *elt;
struct oz_app_hdr *app_hdr;
struct oz_serial_ctx *ctx;
spin_lock_bh(&g_cdev.lock);
pd = g_cdev.active_pd;
if (pd)
... | 33,191,172,042,980,295,000,000,000,000,000,000,000 | ozcdev.c | 132,604,815,029,829,930,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4513 | Buffer overflow in the oz_cdev_write function in drivers/staging/ozwpan/ozcdev.c in the Linux kernel before 3.12 allows local users to cause a denial of service or possibly have unspecified other impact via a crafted write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-4513 |
158,763 | linux | c2c65cd2e14ada6de44cb527e7f1990bede24e15 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c2c65cd2e14ada6de44cb527e7f1990bede24e15 | staging: ozwpan: prevent overflow in oz_cdev_write()
We need to check "count" so we don't overflow the ei->data buffer.
Reported-by: Nico Golde <nico@ngolde.de>
Reported-by: Fabian Yamaguchi <fabs@goesec.de>
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Cc: stable@kernel.org
Signed-off-by: Linus Torvalds <t... | 0 | static ssize_t oz_cdev_write(struct file *filp, const char __user *buf,
size_t count, loff_t *fpos)
{
struct oz_pd *pd;
struct oz_elt_buf *eb;
struct oz_elt_info *ei;
struct oz_elt *elt;
struct oz_app_hdr *app_hdr;
struct oz_serial_ctx *ctx;
if (count > sizeof(ei->data) - sizeof(*elt) - sizeof(*app_hdr))
... | 268,989,265,383,617,740,000,000,000,000,000,000,000 | ozcdev.c | 237,028,343,997,351,830,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2013-4513 | Buffer overflow in the oz_cdev_write function in drivers/staging/ozwpan/ozcdev.c in the Linux kernel before 3.12 allows local users to cause a denial of service or possibly have unspecified other impact via a crafted write operation. | https://nvd.nist.gov/vuln/detail/CVE-2013-4513 |
956 | linux | 6062a8dc0517bce23e3c2f7d2fea5e22411269a3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6062a8dc0517bce23e3c2f7d2fea5e22411269a3 | ipc,sem: fine grained locking for semtimedop
Introduce finer grained locking for semtimedop, to handle the common case
of a program wanting to manipulate one semaphore from an array with
multiple semaphores.
If the call is a semop manipulating just one semaphore in an array with
multiple semaphores, only take the loc... | 1 | void ipc_rcu_putref(void *ptr)
{
if (--container_of(ptr, struct ipc_rcu_hdr, data)->refcount > 0)
return;
if (container_of(ptr, struct ipc_rcu_hdr, data)->is_vmalloc) {
call_rcu(&container_of(ptr, struct ipc_rcu_grace, data)->rcu,
ipc_schedule_free);
} else {
kfree_rcu(container_of(ptr, struct ipc_rc... | 147,913,652,096,999,230,000,000,000,000,000,000,000 | util.c | 17,292,951,975,649,307,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4483 | The ipc_rcu_putref function in ipc/util.c in the Linux kernel before 3.10 does not properly manage a reference count, which allows local users to cause a denial of service (memory consumption or system crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-4483 |
158,781 | linux | 6062a8dc0517bce23e3c2f7d2fea5e22411269a3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6062a8dc0517bce23e3c2f7d2fea5e22411269a3 | ipc,sem: fine grained locking for semtimedop
Introduce finer grained locking for semtimedop, to handle the common case
of a program wanting to manipulate one semaphore from an array with
multiple semaphores.
If the call is a semop manipulating just one semaphore in an array with
multiple semaphores, only take the loc... | 0 | void ipc_rcu_putref(void *ptr)
{
if (!atomic_dec_and_test(&container_of(ptr, struct ipc_rcu_hdr, data)->refcount))
return;
if (container_of(ptr, struct ipc_rcu_hdr, data)->is_vmalloc) {
call_rcu(&container_of(ptr, struct ipc_rcu_grace, data)->rcu,
ipc_schedule_free);
} else {
kfree_rcu(container_of(p... | 197,603,455,992,421,620,000,000,000,000,000,000,000 | util.c | 44,742,915,001,977,680,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4483 | The ipc_rcu_putref function in ipc/util.c in the Linux kernel before 3.10 does not properly manage a reference count, which allows local users to cause a denial of service (memory consumption or system crash) via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-4483 |
957 | linux | e93b7d748be887cd7639b113ba7d7ef792a7efb9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e93b7d748be887cd7639b113ba7d7ef792a7efb9 | ip_output: do skb ufo init for peeked non ufo skb as well
Now, if user application does:
sendto len<mtu flag MSG_MORE
sendto len>mtu flag 0
The skb is not treated as fragmented one because it is not initialized
that way. So move the initialization to fix this.
introduced by:
commit e89e9cf539a28df7d0eb1d0a545368e9920... | 1 | static inline int ip_ufo_append_data(struct sock *sk,
struct sk_buff_head *queue,
int getfrag(void *from, char *to, int offset, int len,
int odd, struct sk_buff *skb),
void *from, int length, int hh_len, int fragheaderlen,
int transhdrlen, int maxfraglen, unsigned int flags)
{
struct sk_buff *skb... | 119,382,236,388,357,000,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-4470 | The Linux kernel before 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly initialize certain data structures, which allows local users to cause a denial of service (memory corruption and system crash) or possibly gain privileges via a crafted application that uses the UDP_CORK option in a setsock... | https://nvd.nist.gov/vuln/detail/CVE-2013-4470 |
158,782 | linux | e93b7d748be887cd7639b113ba7d7ef792a7efb9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e93b7d748be887cd7639b113ba7d7ef792a7efb9 | ip_output: do skb ufo init for peeked non ufo skb as well
Now, if user application does:
sendto len<mtu flag MSG_MORE
sendto len>mtu flag 0
The skb is not treated as fragmented one because it is not initialized
that way. So move the initialization to fix this.
introduced by:
commit e89e9cf539a28df7d0eb1d0a545368e9920... | 0 | static inline int ip_ufo_append_data(struct sock *sk,
struct sk_buff_head *queue,
int getfrag(void *from, char *to, int offset, int len,
int odd, struct sk_buff *skb),
void *from, int length, int hh_len, int fragheaderlen,
int transhdrlen, int maxfraglen, unsigned int flags)
{
struct sk_buff *skb... | 195,049,335,243,193,850,000,000,000,000,000,000,000 | None | null | [
"CWE-264"
] | CVE-2013-4470 | The Linux kernel before 3.12, when UDP Fragmentation Offload (UFO) is enabled, does not properly initialize certain data structures, which allows local users to cause a denial of service (memory corruption and system crash) or possibly gain privileges via a crafted application that uses the UDP_CORK option in a setsock... | https://nvd.nist.gov/vuln/detail/CVE-2013-4470 |
962 | linux | d661684cf6820331feae71146c35da83d794467e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d661684cf6820331feae71146c35da83d794467e | net: Check the correct namespace when spoofing pid over SCM_RIGHTS
This is a security bug.
The follow-up will fix nsproxy to discourage this type of issue from
happening again.
Cc: stable@vger.kernel.org
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
Sig... | 1 | static __inline__ int scm_check_creds(struct ucred *creds)
{
const struct cred *cred = current_cred();
kuid_t uid = make_kuid(cred->user_ns, creds->uid);
kgid_t gid = make_kgid(cred->user_ns, creds->gid);
if (!uid_valid(uid) || !gid_valid(gid))
return -EINVAL;
if ((creds->pid == task_tgid_vnr(current) ||
... | 113,094,377,788,410,970,000,000,000,000,000,000,000 | scm.c | 87,676,516,371,579,840,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-4300 | The scm_check_creds function in net/core/scm.c in the Linux kernel before 3.11 performs a capability check in an incorrect namespace, which allows local users to gain privileges via PID spoofing. | https://nvd.nist.gov/vuln/detail/CVE-2013-4300 |
158,785 | linux | d661684cf6820331feae71146c35da83d794467e | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/d661684cf6820331feae71146c35da83d794467e | net: Check the correct namespace when spoofing pid over SCM_RIGHTS
This is a security bug.
The follow-up will fix nsproxy to discourage this type of issue from
happening again.
Cc: stable@vger.kernel.org
Signed-off-by: Andy Lutomirski <luto@amacapital.net>
Reviewed-by: "Eric W. Biederman" <ebiederm@xmission.com>
Sig... | 0 | static __inline__ int scm_check_creds(struct ucred *creds)
{
const struct cred *cred = current_cred();
kuid_t uid = make_kuid(cred->user_ns, creds->uid);
kgid_t gid = make_kgid(cred->user_ns, creds->gid);
if (!uid_valid(uid) || !gid_valid(gid))
return -EINVAL;
if ((creds->pid == task_tgid_vnr(current) ||
... | 326,123,974,824,909,650,000,000,000,000,000,000,000 | scm.c | 151,933,687,966,539,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2013-4300 | The scm_check_creds function in net/core/scm.c in the Linux kernel before 3.11 performs a capability check in an incorrect namespace, which allows local users to gain privileges via PID spoofing. | https://nvd.nist.gov/vuln/detail/CVE-2013-4300 |
964 | linux | 2433c8f094a008895e66f25bd1773cdb01c91d01 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2433c8f094a008895e66f25bd1773cdb01c91d01 | net: Update the sysctl permissions handler to test effective uid/gid
Modify the code to use current_euid(), and in_egroup_p, as in done
in fs/proc/proc_sysctl.c:test_perm()
Cc: stable@vger.kernel.org
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Reported-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Eric W. ... | 1 | static int net_ctl_permissions(struct ctl_table_header *head,
struct ctl_table *table)
{
struct net *net = container_of(head->set, struct net, sysctls);
kuid_t root_uid = make_kuid(net->user_ns, 0);
kgid_t root_gid = make_kgid(net->user_ns, 0);
/* Allow network administrator to have same access as root... | 4,251,532,209,852,224,000,000,000,000,000,000,000 | sysctl_net.c | 256,848,416,992,939,300,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4270 | The net_ctl_permissions function in net/sysctl_net.c in the Linux kernel before 3.11.5 does not properly determine uid and gid values, which allows local users to bypass intended /proc/sys/net restrictions via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-4270 |
158,787 | linux | 2433c8f094a008895e66f25bd1773cdb01c91d01 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2433c8f094a008895e66f25bd1773cdb01c91d01 | net: Update the sysctl permissions handler to test effective uid/gid
Modify the code to use current_euid(), and in_egroup_p, as in done
in fs/proc/proc_sysctl.c:test_perm()
Cc: stable@vger.kernel.org
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Reported-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Eric W. ... | 0 | static int net_ctl_permissions(struct ctl_table_header *head,
struct ctl_table *table)
{
struct net *net = container_of(head->set, struct net, sysctls);
kuid_t root_uid = make_kuid(net->user_ns, 0);
kgid_t root_gid = make_kgid(net->user_ns, 0);
/* Allow network administrator to have same access as root... | 241,132,518,628,474,020,000,000,000,000,000,000,000 | sysctl_net.c | 267,457,250,745,715,450,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4270 | The net_ctl_permissions function in net/sysctl_net.c in the Linux kernel before 3.11.5 does not properly determine uid and gid values, which allows local users to bypass intended /proc/sys/net restrictions via a crafted application. | https://nvd.nist.gov/vuln/detail/CVE-2013-4270 |
965 | FFmpeg | c94f9e854228e0ea00e1de8769d8d3f7cab84a55 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/c94f9e854228e0ea00e1de8769d8d3f7cab84a55 | avutil/mem: Fix flipped condition
Fixes return code and later null pointer dereference
Found-by: Laurent Butti <laurentb@gmail.com>
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 1 | int av_reallocp_array(void *ptr, size_t nmemb, size_t size)
{
void **ptrptr = ptr;
*ptrptr = av_realloc_f(*ptrptr, nmemb, size);
if (!*ptrptr && !(nmemb && size))
return AVERROR(ENOMEM);
return 0;
}
| 104,455,358,682,340,870,000,000,000,000,000,000,000 | mem.c | 308,060,967,527,841,900,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2013-4265 | The av_reallocp_array function in libavutil/mem.c in FFmpeg before 2.0.1 has an unspecified impact and remote vectors related to a "wrong return code" and a resultant NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2013-4265 |
158,788 | FFmpeg | c94f9e854228e0ea00e1de8769d8d3f7cab84a55 | https://github.com/FFmpeg/FFmpeg | https://github.com/FFmpeg/FFmpeg/commit/c94f9e854228e0ea00e1de8769d8d3f7cab84a55 | avutil/mem: Fix flipped condition
Fixes return code and later null pointer dereference
Found-by: Laurent Butti <laurentb@gmail.com>
Signed-off-by: Michael Niedermayer <michaelni@gmx.at> | 0 | int av_reallocp_array(void *ptr, size_t nmemb, size_t size)
{
void **ptrptr = ptr;
*ptrptr = av_realloc_f(*ptrptr, nmemb, size);
if (!*ptrptr && nmemb && size)
return AVERROR(ENOMEM);
return 0;
}
| 249,553,250,920,400,360,000,000,000,000,000,000,000 | mem.c | 148,629,479,801,131,880,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2013-4265 | The av_reallocp_array function in libavutil/mem.c in FFmpeg before 2.0.1 has an unspecified impact and remote vectors related to a "wrong return code" and a resultant NULL pointer dereference. | https://nvd.nist.gov/vuln/detail/CVE-2013-4265 |
977 | linux | c95eb3184ea1a3a2551df57190c81da695e2144b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c95eb3184ea1a3a2551df57190c81da695e2144b | ARM: 7809/1: perf: fix event validation for software group leaders
It is possible to construct an event group with a software event as a
group leader and then subsequently add a hardware event to the group.
This results in the event group being validated by adding all members
of the group to a fake PMU and attempting ... | 1 | validate_event(struct pmu_hw_events *hw_events,
struct perf_event *event)
{
struct arm_pmu *armpmu = to_arm_pmu(event->pmu);
struct pmu *leader_pmu = event->group_leader->pmu;
if (event->pmu != leader_pmu || event->state < PERF_EVENT_STATE_OFF)
return 1;
if (event->state == PERF_EVENT_STATE_OFF &&... | 214,965,441,703,397,300,000,000,000,000,000,000,000 | perf_event.c | 244,258,602,866,703,960,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4254 | The validate_event function in arch/arm/kernel/perf_event.c in the Linux kernel before 3.10.8 on the ARM platform allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by adding a hardware event to an event group led by a software event. | https://nvd.nist.gov/vuln/detail/CVE-2013-4254 |
158,801 | linux | c95eb3184ea1a3a2551df57190c81da695e2144b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c95eb3184ea1a3a2551df57190c81da695e2144b | ARM: 7809/1: perf: fix event validation for software group leaders
It is possible to construct an event group with a software event as a
group leader and then subsequently add a hardware event to the group.
This results in the event group being validated by adding all members
of the group to a fake PMU and attempting ... | 0 | validate_event(struct pmu_hw_events *hw_events,
struct perf_event *event)
{
struct arm_pmu *armpmu = to_arm_pmu(event->pmu);
struct pmu *leader_pmu = event->group_leader->pmu;
if (is_software_event(event))
return 1;
if (event->pmu != leader_pmu || event->state < PERF_EVENT_STATE_OFF)
return 1;
... | 236,960,724,135,439,900,000,000,000,000,000,000,000 | perf_event.c | 260,167,828,169,172,000,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4254 | The validate_event function in arch/arm/kernel/perf_event.c in the Linux kernel before 3.10.8 on the ARM platform allows local users to gain privileges or cause a denial of service (NULL pointer dereference and system crash) by adding a hardware event to an event group led by a software event. | https://nvd.nist.gov/vuln/detail/CVE-2013-4254 |
978 | linux | 1fc29bacedeabb278080e31bb9c1ecb49f143c3b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1fc29bacedeabb278080e31bb9c1ecb49f143c3b | cifs: fix off-by-one bug in build_unc_path_to_root
commit 839db3d10a (cifs: fix up handling of prefixpath= option) changed
the code such that the vol->prepath no longer contained a leading
delimiter and then fixed up the places that accessed that field to
account for that change.
One spot in build_unc_path_to_root wa... | 1 | build_unc_path_to_root(const struct smb_vol *vol,
const struct cifs_sb_info *cifs_sb)
{
char *full_path, *pos;
unsigned int pplen = vol->prepath ? strlen(vol->prepath) + 1 : 0;
unsigned int unc_len = strnlen(vol->UNC, MAX_TREE_SIZE + 1);
full_path = kmalloc(unc_len + pplen + 1, GFP_KERNEL);
if (full_path == NUL... | 8,340,581,254,640,439,000,000,000,000,000,000,000 | connect.c | 127,914,316,993,594,920,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4247 | Off-by-one error in the build_unc_path_to_root function in fs/cifs/connect.c in the Linux kernel before 3.9.6 allows remote attackers to cause a denial of service (memory corruption and system crash) via a DFS share mount operation that triggers use of an unexpected DFS referral name length. | https://nvd.nist.gov/vuln/detail/CVE-2013-4247 |
158,802 | linux | 1fc29bacedeabb278080e31bb9c1ecb49f143c3b | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/1fc29bacedeabb278080e31bb9c1ecb49f143c3b | cifs: fix off-by-one bug in build_unc_path_to_root
commit 839db3d10a (cifs: fix up handling of prefixpath= option) changed
the code such that the vol->prepath no longer contained a leading
delimiter and then fixed up the places that accessed that field to
account for that change.
One spot in build_unc_path_to_root wa... | 0 | build_unc_path_to_root(const struct smb_vol *vol,
const struct cifs_sb_info *cifs_sb)
{
char *full_path, *pos;
unsigned int pplen = vol->prepath ? strlen(vol->prepath) + 1 : 0;
unsigned int unc_len = strnlen(vol->UNC, MAX_TREE_SIZE + 1);
full_path = kmalloc(unc_len + pplen + 1, GFP_KERNEL);
if (full_path == NUL... | 314,585,337,494,192,760,000,000,000,000,000,000,000 | connect.c | 88,857,981,430,770,820,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2013-4247 | Off-by-one error in the build_unc_path_to_root function in fs/cifs/connect.c in the Linux kernel before 3.9.6 allows remote attackers to cause a denial of service (memory corruption and system crash) via a DFS share mount operation that triggers use of an unexpected DFS referral name length. | https://nvd.nist.gov/vuln/detail/CVE-2013-4247 |
979 | libtiff | ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | fix possible OOB write in gif2tiff.c | 1 | process(register int code, unsigned char** fill)
{
int incode;
static unsigned char firstchar;
if (code == clear) {
codesize = datasize + 1;
codemask = (1 << codesize) - 1;
avail = clear + 2;
oldcode = -1;
return 1;
}
if (oldcode == -1) {
*(*fill)++ = suffix[code];
firstchar = oldcode ... | 49,639,759,056,433,870,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-4244 | The LZW decompressor in the gif2tiff tool in libtiff 4.0.3 and earlier allows context-dependent attackers to cause a denial of service (out-of-bounds write and crash) or possibly execute arbitrary code via a crafted GIF image. | https://nvd.nist.gov/vuln/detail/CVE-2013-4244 |
158,803 | libtiff | ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | https://github.com/vadz/libtiff | https://github.com/vadz/libtiff/commit/ce6841d9e41d621ba23cf18b190ee6a23b2cc833 | fix possible OOB write in gif2tiff.c | 0 | process(register int code, unsigned char** fill)
{
int incode;
static unsigned char firstchar;
if (code == clear) {
codesize = datasize + 1;
codemask = (1 << codesize) - 1;
avail = clear + 2;
oldcode = -1;
return 1;
}
if (oldcode == -1) {
if (code >= clear) {
fprintf(st... | 326,773,067,396,447,780,000,000,000,000,000,000,000 | None | null | [
"CWE-119"
] | CVE-2013-4244 | The LZW decompressor in the gif2tiff tool in libtiff 4.0.3 and earlier allows context-dependent attackers to cause a denial of service (out-of-bounds write and crash) or possibly execute arbitrary code via a crafted GIF image. | https://nvd.nist.gov/vuln/detail/CVE-2013-4244 |
980 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 1 | asmlinkage void bad_mode(struct pt_regs *regs, int reason, unsigned int esr)
{
console_verbose();
pr_crit("Bad mode in %s handler detected, code 0x%08x\n",
handler[reason], esr);
die("Oops - bad mode", regs, 0);
local_irq_disable();
panic("bad mode");
}
| 172,340,806,476,661,160,000,000,000,000,000,000,000 | traps.c | 194,636,283,620,040,100,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
158,804 | linux | 9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/9955ac47f4ba1c95ecb6092aeaefb40a22e99268 | arm64: don't kill the kernel on a bad esr from el0
Rather than completely killing the kernel if we receive an esr value we
can't deal with in the el0 handlers, send the process a SIGILL and log
the esr value in the hope that we can debug it. If we receive a bad esr
from el1, we'll die() as before.
Signed-off-by: Mark... | 0 | asmlinkage void bad_mode(struct pt_regs *regs, int reason, unsigned int esr)
{
siginfo_t info;
void __user *pc = (void __user *)instruction_pointer(regs);
console_verbose();
pr_crit("Bad mode in %s handler detected, code 0x%08x\n",
handler[reason], esr);
__show_regs(regs);
info.si_signo = SIGILL;
info.... | 12,305,327,694,614,374,000,000,000,000,000,000,000 | traps.c | 209,503,121,353,299,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-4220 | The bad_mode function in arch/arm64/kernel/traps.c in the Linux kernel before 3.9.5 on the ARM64 platform allows local users to cause a denial of service (system crash) via vectors involving an attempted register access that triggers an unexpected value in the Exception Syndrome Register (ESR). | https://nvd.nist.gov/vuln/detail/CVE-2013-4220 |
982 | linux | 75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | ipv6: ip6_append_data_mtu did not care about pmtudisc and frag_size
If the socket had an IPV6_MTU value set, ip6_append_data_mtu lost track
of this when appending the second frame on a corked socket. This results
in the following splat:
[37598.993962] ------------[ cut here ]------------
[37598.994008] kernel BUG at ... | 1 | static void ip6_append_data_mtu(int *mtu,
int *maxfraglen,
unsigned int fragheaderlen,
struct sk_buff *skb,
struct rt6_info *rt)
{
if (!(rt->dst.flags & DST_XFRM_TUNNEL)) {
if (skb == NULL) {
/* first fragment, reserve header_len */
*mtu = *mtu - rt->dst.header_len;
} else {
/*
... | 249,477,262,173,279,060,000,000,000,000,000,000,000 | ip6_output.c | 32,175,030,324,283,845,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4163 | The ip6_append_data_mtu function in net/ipv6/ip6_output.c in the IPv6 implementation in the Linux kernel through 3.10.3 does not properly maintain information about whether the IPV6_MTU setsockopt option had been specified, which allows local users to cause a denial of service (BUG and system crash) via a crafted appli... | https://nvd.nist.gov/vuln/detail/CVE-2013-4163 |
158,806 | linux | 75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/75a493e60ac4bbe2e977e7129d6d8cbb0dd236be | ipv6: ip6_append_data_mtu did not care about pmtudisc and frag_size
If the socket had an IPV6_MTU value set, ip6_append_data_mtu lost track
of this when appending the second frame on a corked socket. This results
in the following splat:
[37598.993962] ------------[ cut here ]------------
[37598.994008] kernel BUG at ... | 0 | static void ip6_append_data_mtu(int *mtu,
static void ip6_append_data_mtu(unsigned int *mtu,
int *maxfraglen,
unsigned int fragheaderlen,
struct sk_buff *skb,
struct rt6_info *rt,
bool pmtuprobe)
{
if (!(rt->dst.flags & DST_XFRM_TUNNEL)) {
if (skb == NULL) {
/* first fragment, reserve he... | 46,361,514,097,780,460,000,000,000,000,000,000,000 | None | null | [
"CWE-399"
] | CVE-2013-4163 | The ip6_append_data_mtu function in net/ipv6/ip6_output.c in the IPv6 implementation in the Linux kernel through 3.10.3 does not properly maintain information about whether the IPV6_MTU setsockopt option had been specified, which allows local users to cause a denial of service (BUG and system crash) via a crafted appli... | https://nvd.nist.gov/vuln/detail/CVE-2013-4163 |
984 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 1 | static int udp_v6_push_pending_frames(struct sock *sk)
{
struct sk_buff *skb;
struct udphdr *uh;
struct udp_sock *up = udp_sk(sk);
struct inet_sock *inet = inet_sk(sk);
struct flowi6 *fl6 = &inet->cork.fl.u.ip6;
int err = 0;
int is_udplite = IS_UDPLITE(sk);
__wsum csum = 0;
/* Grab the skbuff where U... | 308,814,749,542,050,950,000,000,000,000,000,000,000 | udp.c | 46,858,807,665,352,770,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
158,808 | linux | 8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/8822b64a0fa64a5dd1dfcf837c5b0be83f8c05d1 | ipv6: call udp_push_pending_frames when uncorking a socket with AF_INET pending data
We accidentally call down to ip6_push_pending_frames when uncorking
pending AF_INET data on a ipv6 socket. This results in the following
splat (from Dave Jones):
skbuff: skb_under_panic: text:ffffffff816765f6 len:48 put:40 head:ffff8... | 0 | static int udp_v6_push_pending_frames(struct sock *sk)
{
struct sk_buff *skb;
struct udphdr *uh;
struct udp_sock *up = udp_sk(sk);
struct inet_sock *inet = inet_sk(sk);
struct flowi6 *fl6;
int err = 0;
int is_udplite = IS_UDPLITE(sk);
__wsum csum = 0;
if (up->pending == AF_INET)
return udp_push_pend... | 158,302,249,836,920,260,000,000,000,000,000,000,000 | udp.c | 67,886,294,310,334,220,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4162 | The udp_v6_push_pending_frames function in net/ipv6/udp.c in the IPv6 implementation in the Linux kernel through 3.10.3 makes an incorrect function call for pending data, which allows local users to cause a denial of service (BUG and system crash) via a crafted application that uses the UDP_CORK option in a setsockopt ... | https://nvd.nist.gov/vuln/detail/CVE-2013-4162 |
985 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 1 | static int __br_mdb_del(struct net_bridge *br, struct br_mdb_entry *entry)
{
struct net_bridge_mdb_htable *mdb;
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
struct br_ip ip;
int err = -EINVAL;
if (!netif_running(br->dev) || br->multicast_disabled)
... | 182,535,534,055,103,100,000,000,000,000,000,000,000 | br_mdb.c | 276,386,508,481,368,340,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
158,809 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static int __br_mdb_del(struct net_bridge *br, struct br_mdb_entry *entry)
{
struct net_bridge_mdb_htable *mdb;
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
struct br_ip ip;
int err = -EINVAL;
if (!netif_running(br->dev) || br->multicast_disabled)
... | 235,621,052,503,688,060,000,000,000,000,000,000,000 | br_mdb.c | 123,212,080,278,406,970,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
986 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 1 | static void br_multicast_del_pg(struct net_bridge *br,
struct net_bridge_port_group *pg)
{
struct net_bridge_mdb_htable *mdb;
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
mdb = mlock_dereference(br->mdb, br);
mp = br_mdb_ip_get(mdb, &pg->addr);
... | 74,664,793,578,988,530,000,000,000,000,000,000,000 | br_multicast.c | 3,552,800,112,656,103,400,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
158,810 | linux | c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/c7e8e8a8f7a70b343ca1e0f90a31e35ab2d16de1 | bridge: fix some kernel warning in multicast timer
Several people reported the warning: "kernel BUG at kernel/timer.c:729!"
and the stack trace is:
#7 [ffff880214d25c10] mod_timer+501 at ffffffff8106d905
#8 [ffff880214d25c50] br_multicast_del_pg.isra.20+261 at ffffffffa0731d25 [bridge]
#9 [ffff880214d25c80] br_mul... | 0 | static void br_multicast_del_pg(struct net_bridge *br,
struct net_bridge_port_group *pg)
{
struct net_bridge_mdb_htable *mdb;
struct net_bridge_mdb_entry *mp;
struct net_bridge_port_group *p;
struct net_bridge_port_group __rcu **pp;
mdb = mlock_dereference(br->mdb, br);
mp = br_mdb_ip_get(mdb, &pg->addr);
... | 156,391,368,179,806,070,000,000,000,000,000,000,000 | br_multicast.c | 184,713,466,390,494,330,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2013-4129 | The bridge multicast implementation in the Linux kernel through 3.10.3 does not check whether a certain timer is armed before modifying the timeout value of that timer, which allows local users to cause a denial of service (BUG and system crash) via vectors involving the shutdown of a KVM virtual machine, related to ne... | https://nvd.nist.gov/vuln/detail/CVE-2013-4129 |
987 | linux | dd7633ecd553a5e304d349aa6f8eb8a0417098c5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dd7633ecd553a5e304d349aa6f8eb8a0417098c5 | vhost-net: fix use-after-free in vhost_net_flush
vhost_net_ubuf_put_and_wait has a confusing name:
it will actually also free it's argument.
Thus since commit 1280c27f8e29acf4af2da914e80ec27c3dbd5c01
"vhost-net: flush outstanding DMAs on memory change"
vhost_net_flush tries to use the argument after passing it
to ... | 1 | static long vhost_net_set_backend(struct vhost_net *n, unsigned index, int fd)
{
struct socket *sock, *oldsock;
struct vhost_virtqueue *vq;
struct vhost_net_virtqueue *nvq;
struct vhost_net_ubuf_ref *ubufs, *oldubufs = NULL;
int r;
mutex_lock(&n->dev.mutex);
r = vhost_dev_check_owner(&n->dev);
if (r)
goto er... | 241,366,389,520,784,070,000,000,000,000,000,000,000 | net.c | 277,417,259,469,627,080,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4127 | Use-after-free vulnerability in the vhost_net_set_backend function in drivers/vhost/net.c in the Linux kernel through 3.10.3 allows local users to cause a denial of service (OOPS and system crash) via vectors involving powering on a virtual machine. | https://nvd.nist.gov/vuln/detail/CVE-2013-4127 |
158,811 | linux | dd7633ecd553a5e304d349aa6f8eb8a0417098c5 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dd7633ecd553a5e304d349aa6f8eb8a0417098c5 | vhost-net: fix use-after-free in vhost_net_flush
vhost_net_ubuf_put_and_wait has a confusing name:
it will actually also free it's argument.
Thus since commit 1280c27f8e29acf4af2da914e80ec27c3dbd5c01
"vhost-net: flush outstanding DMAs on memory change"
vhost_net_flush tries to use the argument after passing it
to ... | 0 | static long vhost_net_set_backend(struct vhost_net *n, unsigned index, int fd)
{
struct socket *sock, *oldsock;
struct vhost_virtqueue *vq;
struct vhost_net_virtqueue *nvq;
struct vhost_net_ubuf_ref *ubufs, *oldubufs = NULL;
int r;
mutex_lock(&n->dev.mutex);
r = vhost_dev_check_owner(&n->dev);
if (r)
goto er... | 337,150,261,346,638,500,000,000,000,000,000,000,000 | net.c | 61,901,905,992,146,420,000,000,000,000,000,000,000 | [
"CWE-399"
] | CVE-2013-4127 | Use-after-free vulnerability in the vhost_net_set_backend function in drivers/vhost/net.c in the Linux kernel through 3.10.3 allows local users to cause a denial of service (OOPS and system crash) via vectors involving powering on a virtual machine. | https://nvd.nist.gov/vuln/detail/CVE-2013-4127 |
992 | linux | ea702b80e0bbb2448e201472127288beb82ca2fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea702b80e0bbb2448e201472127288beb82ca2fe | cifs: move check for NULL socket into smb_send_rqst
Cai reported this oops:
[90701.616664] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
[90701.625438] IP: [<ffffffff814a343e>] kernel_setsockopt+0x2e/0x60
[90701.632167] PGD fea319067 PUD 103fda4067 PMD 0
[90701.637255] Oops: 0000 [#1] SMP
... | 1 | smb_send_rqst(struct TCP_Server_Info *server, struct smb_rqst *rqst)
{
int rc;
struct kvec *iov = rqst->rq_iov;
int n_vec = rqst->rq_nvec;
unsigned int smb_buf_length = get_rfc1002_length(iov[0].iov_base);
unsigned int i;
size_t total_len = 0, sent;
struct socket *ssocket = server->ssocket;
int val = 1;
c... | 125,179,843,386,250,260,000,000,000,000,000,000,000 | transport.c | 274,077,842,134,574,640,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2013-3302 | Race condition in the smb_send_rqst function in fs/cifs/transport.c in the Linux kernel before 3.7.2 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact via vectors involving a reconnection event. | https://nvd.nist.gov/vuln/detail/CVE-2013-3302 |
158,815 | linux | ea702b80e0bbb2448e201472127288beb82ca2fe | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/ea702b80e0bbb2448e201472127288beb82ca2fe | cifs: move check for NULL socket into smb_send_rqst
Cai reported this oops:
[90701.616664] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
[90701.625438] IP: [<ffffffff814a343e>] kernel_setsockopt+0x2e/0x60
[90701.632167] PGD fea319067 PUD 103fda4067 PMD 0
[90701.637255] Oops: 0000 [#1] SMP
... | 0 | smb_send_rqst(struct TCP_Server_Info *server, struct smb_rqst *rqst)
{
int rc;
struct kvec *iov = rqst->rq_iov;
int n_vec = rqst->rq_nvec;
unsigned int smb_buf_length = get_rfc1002_length(iov[0].iov_base);
unsigned int i;
size_t total_len = 0, sent;
struct socket *ssocket = server->ssocket;
int val = 1;
if... | 199,790,013,741,477,500,000,000,000,000,000,000,000 | transport.c | 109,712,433,639,111,850,000,000,000,000,000,000,000 | [
"CWE-362"
] | CVE-2013-3302 | Race condition in the smb_send_rqst function in fs/cifs/transport.c in the Linux kernel before 3.7.2 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact via vectors involving a reconnection event. | https://nvd.nist.gov/vuln/detail/CVE-2013-3302 |
993 | linux | 6a76f8c0ab19f215af2a3442870eeb5f0e81998d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6a76f8c0ab19f215af2a3442870eeb5f0e81998d | tracing: Fix possible NULL pointer dereferences
Currently set_ftrace_pid and set_graph_function files use seq_lseek
for their fops. However seq_open() is called only for FMODE_READ in
the fops->open() so that if an user tries to seek one of those file
when she open it for writing, it sees NULL seq_file and then panic... | 1 | ftrace_regex_lseek(struct file *file, loff_t offset, int whence)
{
loff_t ret;
if (file->f_mode & FMODE_READ)
ret = seq_lseek(file, offset, whence);
else
file->f_pos = ret = 1;
return ret;
}
| 93,795,587,963,981,600,000,000,000,000,000,000,000 | ftrace.c | 76,813,553,117,675,730,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2013-3301 | The ftrace implementation in the Linux kernel before 3.8.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging the CAP_SYS_ADMIN capability for write access to the (1) set_ftrace_pid or (2) set_graph_function file, and then ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3301 |
158,816 | linux | 6a76f8c0ab19f215af2a3442870eeb5f0e81998d | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/6a76f8c0ab19f215af2a3442870eeb5f0e81998d | tracing: Fix possible NULL pointer dereferences
Currently set_ftrace_pid and set_graph_function files use seq_lseek
for their fops. However seq_open() is called only for FMODE_READ in
the fops->open() so that if an user tries to seek one of those file
when she open it for writing, it sees NULL seq_file and then panic... | 0 | ftrace_regex_lseek(struct file *file, loff_t offset, int whence)
ftrace_filter_lseek(struct file *file, loff_t offset, int whence)
{
loff_t ret;
if (file->f_mode & FMODE_READ)
ret = seq_lseek(file, offset, whence);
else
file->f_pos = ret = 1;
return ret;
}
| 262,024,129,485,182,500,000,000,000,000,000,000,000 | None | null | [
"CWE-703"
] | CVE-2013-3301 | The ftrace implementation in the Linux kernel before 3.8.8 allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact by leveraging the CAP_SYS_ADMIN capability for write access to the (1) set_ftrace_pid or (2) set_graph_function file, and then ... | https://nvd.nist.gov/vuln/detail/CVE-2013-3301 |
1,003 | linux | b860d3cc62877fad02863e2a08efff69a19382d2 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b860d3cc62877fad02863e2a08efff69a19382d2 | l2tp: fix info leak in l2tp_ip6_recvmsg()
The L2TP code for IPv6 fails to initialize the l2tp_conn_id member of
struct sockaddr_l2tpip6 and therefore leaks four bytes kernel stack
in l2tp_ip6_recvmsg() in case msg_name is set.
Initialize l2tp_conn_id with 0 to avoid the info leak.
Signed-off-by: Mathias Krause <mini... | 1 | static int l2tp_ip6_recvmsg(struct kiocb *iocb, struct sock *sk,
struct msghdr *msg, size_t len, int noblock,
int flags, int *addr_len)
{
struct ipv6_pinfo *np = inet6_sk(sk);
struct sockaddr_l2tpip6 *lsa = (struct sockaddr_l2tpip6 *)msg->msg_name;
size_t copied = 0;
int err = -EOPNOTSUPP;
struct sk_... | 153,456,865,559,495,400,000,000,000,000,000,000,000 | None | null | [
"CWE-200"
] | CVE-2013-3230 | The l2tp_ip6_recvmsg function in net/l2tp/l2tp_ip6.c in the Linux kernel before 3.9-rc7 does not initialize a certain structure member, which allows local users to obtain sensitive information from kernel stack memory via a crafted recvmsg or recvfrom system call. | https://nvd.nist.gov/vuln/detail/CVE-2013-3230 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.